See the supported connectors for Application Integration.

Introduction to logs

This page describes the different types of logs available for Application Integration and when to use them.

Overview

Application Integration enables you to generate logs for your integration executions. You can use these logs to troubleshoot execution failures, monitor usage, or set alerts. There are two ways of viewing your logs:

  • Integration execution logs. These logs are generated when integrations are executed. These logs can either be viewed in Application Integration and Cloud Logging.
  • Audit logs. With audit logs you can understand who did what, where, and when within your integration. These logs can be only be viewed in Cloud Logging with no extra charges incurred by the logs.

With Application Integration, you can leverage Cloud Logging features including setting alerts on these logs and custom retention by storing execution logs in Cloud Logging.

Application Integration logs

When you execute an integration, the execution logs are generated for that integration and stored in the region where you created your integration. You can access these logs to troubleshoot errors and view the status of each step in an integration. The following image displays the Execution Logs page:

image showing the Execution Logs page iimage showing the Execution Logs page

For more information about viewing logs in Application Integration, see Integration execution logs.

Cloud Logging

Cloud Logging is a real-time log-management system with storage, search, analysis, and monitoring support. With Application Integration, you can leverage Cloud Logging features. By default, Cloud Logging is disabled for integrations. You can enable logging for an integration by editing the unpublished version of the integration.

Cloud Logging captures integration runtime logs for the following levels of severity:

  • Info: Logs containing executions logs and other details related to all integration executions: SUCCEEDED, FAILED, PROCESSING, PENDING, SUSPENDED, and CANCELLED.
  • Error and Warning: Logs containing executions logs and other details related to the FAILED and CANCELLED integration execution states.

    • For a list of integration execution states, see Execution states.

For information about how to view logs in Cloud Logging, see View integration logs in Cloud Logging.

Log buckets

Integration execution logs are stored in the _Default bucket with the default storage location configured. You can route logs to different destinations:

  • Send logs to different log buckets with different storage locations using inclusion and exclusion filters of Cloud Logging.
  • Export the logs to different destinations like BigQuery or Pub/Sub.

For more information about Cloud Logging routing and storage, see Routing and storage overview.

Audit logs

For information about audit logs, see View audit logs.

Pricing

Application Integration logs don't have any additional costs but audit logs and Cloud Logging have different pricing models. For information about pricing for Cloud Logging, see Cloud Logging pricing.

Limitations

Integration logs are subject to the following limitations:

  • Cloud Logging only supports log entries that are up to 256 KiB in size. If your logs exceed this limit, the request and response parameters are not shown in the logging details. For information about Cloud Logging quotas and limits, see Quotas and limits. To resolve this error, modify the value of the integration variables so that the value doesn't exceed the limit. Alternatively, you can also view these logs in Application Integration. This limitation is applicable to Cloud Logging logs.
  • If local logging is disabled, the execution logs are not sent to Cloud Logging even if Cloud Logging is enabled. This limitation is applicable to both Integration execution logs and Cloud Logging logs.

What's next