Preview

This product or feature is covered by the Pre-GA Offerings Terms of the Google Cloud Terms of Service. Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. For more information, see the launch stage descriptions.

See the supported connectors for Application Integration.

Integration execution logs

Application Integration generates execution log messages for each run of an integration. The log messages contain information that can be helpful in determining the status of each step in an integration, or to troubleshoot a failed integration, task, or event.

Note: Application Integration retains the execution logs of an integration for a maximum period of 32 days.

To view the Execution Logs page, open your integration and click Logs in the integration designer toolbar. To view region specific execution logs of the integration, select a region using the available drop-down menu. You can also click Refresh Logs to reload the current log list.

The following attributes are displayed for each execution log message.

• Integration name: Name of the integration.
• Execution ID: An unique identifier generated for each run of an integration.
• Status: Status of the integration execution.
  • Succeeded: Indicates that the integration executed successfully.
  • Failed: Indicates that the integration failed to execute.
  • Canceled: Indicates that the integration execution was canceled by the user.
  • On hold: Indicates that the integration execution is temporarily paused and is waiting for an event or action to be completed.
• Start time: Timestamp of when the integration started execution.
• Duration: Time taken for execution of the integration.
  Note: Don't use the Duration value to calculate the end-to-end execution latency of an integration. The time displayed in the Duration column does not reflect the total execution time of an integration, as it doesn't account for any of the additional time taken by the integration before or after its execution. For example, time taken for quota enforcement or authentication is not reflected in the Duration value.
• Integration Version: Version of the integration executed.
• Trigger ID: ID value of the trigger.

You can filter the logs based on criteria such as, integration name, execution ID, date or time range, execution status, variable type, and variable name or value. To add filters, click Add a filter in the Execution Logs page.

The following image shows a sample Application Integration Execution Logs page.

Use logs to troubleshoot integration failures

Execution log messages can be valuable resources when troubleshooting unsuccessful integration runs.

For example, if an integration failed to run in a specific timeframe, use these steps to access and filter the logs to troubleshoot the failure:

1. Search for or select the integration to troubleshoot from the Integrations list and click to open the integration designer.
2. Click Logs in the toolbar of the integration designer to view the log messages.
3. Click Add a filter to display the list of available filters.
4. Select Integration name.
5. Enter the integration name, then click Apply.
6. Click Add a filter to display the list of available filters.
7. Select Execution status to display the status list.
8. Select the FAILED checkbox, then click Apply to display failed integrations.
9. Click Add a filter to display the list of available filters.
10. Select Date/time range and enter the desired time range to check for failure. For example, enter:
    • From Date: Select 2020-12-16
    • From Time: Select 04:00:00 PM
    • To Date: Select 2019-12-16
    • To Time: Select 05:00:00 PM
    Multiple filters are combined using the AND condition by default.
    • Click Apply.

If the integration failed during the filtered time frame, the Execution Logs page displays a list of log messages. Each log message corresponds to a specific failed run of the integration.

Use logs to view stack trace exceptions

To view the list of exceptions, click on any log message. Click the links in each exception message to view the complete stack trace of the exception.

Note: Execution log message event parameters (string or JSON) are truncated with a limit of 2000 characters.

Use logs to troubleshoot and trace connector failures

You can use the execution log messages to troubleshoot and trace failed connectors task executions. Log data of a failed connector task is stored using Cloud Logging and can be viewed in the Logs Explorer.

Note: Log data of a failed connectors task is available in Logs Explorer only if Cloud Logging is enabled for the respective connection in Integration Connectors. See View connector logs for more details.

Perform the following steps to access the log data of a failed connector task from Application Integration:

1. Go to the Execution Logs page of your desired integration.
2. Expand the log message of your failed execution, and stack trace to the row containing the failed Connectors task.
3. In the Status column, click Failed.

   

Application Integration automatically runs the required query for the failed connectors task and opens the Logs Explorer page to display the detailed execution log data.

To manually retrieve the log data of a failed connectors task, you can run the following query in the Logs Explorer's Query page. For more information about how to use Logs Explorer, see Logs Explorer interface.

Query format

resource.type="connectors.googleapis.com/Connection"
jsonPayload.integration_connectors_trace_id="EXECUTION_ID_EXECUTION_TASK_ID_EXECUTION_ATTEMPT_NUMBER"

Example

resource.type="connectors.googleapis.com/Connection"
jsonPayload.integration_connectors_trace_id="9db51e4b-7d57-473d-931f-cc27b282dfad_1_2"