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:
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.
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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eApplication Integration generates execution logs for each integration, which can be used for troubleshooting, monitoring, and setting alerts, and can be viewed in both Application Integration and Cloud Logging.\u003c/p\u003e\n"],["\u003cp\u003eAudit logs, which track who did what, where, and when within an integration, are available exclusively in Cloud Logging at no extra cost.\u003c/p\u003e\n"],["\u003cp\u003eCloud Logging, when enabled, captures integration runtime logs with different levels of severity such as Info, Error, and Warning, and can have logs sent to different buckets with different storage locations.\u003c/p\u003e\n"],["\u003cp\u003eCloud Logging has a limitation of 256 KiB per log entry; logs exceeding this size will not show request and response parameters, but they can still be viewed within Application Integration.\u003c/p\u003e\n"],["\u003cp\u003eIntegration logs are affected by local logging settings, so if local logging is disabled then execution logs are not sent to Cloud Logging even if it is enabled.\u003c/p\u003e\n"]]],[],null,["# Introduction to logs\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nIntroduction to logs\n====================\n\n\nThis page describes the different types of logs available for Application Integration and when to use them.\n\nOverview\n--------\n\n\nApplication Integration enables you to generate logs for your integration executions. You can use these\nlogs to troubleshoot execution failures, monitor usage, or set alerts. There are two ways\nof viewing your logs:\n\n- **Integration execution logs.** These logs are generated when integrations are executed. These logs can either be viewed in [Application Integration](#integration-logs) and [Cloud Logging](#cloud-logs).\n- **Audit logs.** With [audit logs](#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.\n\n\u003cbr /\u003e\n\nWith Application Integration, you can leverage Cloud Logging features including setting alerts on these logs and custom retention by storing execution logs in Cloud Logging.\n\nApplication Integration logs\n----------------------------\n\nWhen 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.\nThe following image displays the **Execution Logs** page:\n\n\nFor more information about viewing logs in Application Integration, see [Integration execution logs](/application-integration/docs/integration-execution-logs).\n\nCloud Logging\n-------------\n\n[Cloud Logging](/logging/docs/overview) 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](/application-integration/docs/cloud-logging#before-you-begin) by editing the unpublished version of the integration.\n\n\nCloud Logging captures integration runtime logs for the following levels of severity:\n\n- **Info:** Logs containing executions logs and other details related to all integration executions: `SUCCEEDED`, `FAILED`, `PROCESSING`, `PENDING`, `SUSPENDED`, and `CANCELLED`.\n- **Error and Warning:** Logs containing executions logs and other details related to the `FAILED` and `CANCELLED` integration execution states.\n- For a list of integration execution states, see [Execution states](/application-integration/docs/reference/rest/v1/projects.locations.integrations.executions#state).\n\nFor information about how to view logs in Cloud Logging, see [View integration logs in Cloud Logging](/application-integration/docs/cloud-logging).\n| **Note:** 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. In that case, you can update the integration variables so that the value doesn't exceed the limit. Alternatively, you can [view these logs in Application Integration](/application-integration/docs/integration-execution-logs).\n\n### Log buckets\n\nIntegration execution logs are stored in the `_Default` bucket with the default storage location configured. You can route logs to different destinations:\n\n- Send logs to different log buckets with different storage locations using inclusion and exclusion filters of Cloud Logging.\n- Export the logs to different destinations like BigQuery or Pub/Sub.\n\nFor more information about Cloud Logging routing and storage, see [Routing and storage overview](/logging/docs/routing/overview).\n\nAudit logs\n----------\n\n\nFor information about audit logs, see [View audit logs](/application-integration/docs/audit-logging).\n\nPricing\n-------\n\nApplication Integration logs don't have any additional costs but audit logs and Cloud Logging have different pricing models.\nFor information about pricing for Cloud Logging, see [Cloud Logging pricing](/stackdriver/pricing#logging-costs).\n\nLimitations\n-----------\n\nIntegration logs are subject to the following limitations:\n\n- 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](/logging/quotas). 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](/application-integration/docs/integration-execution-logs). This limitation is applicable to [Cloud Logging logs](/application-integration/docs/cloud-logging).\n- If [local logging](/application-integration/docs/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](/application-integration/docs/integration-execution-logs) and [Cloud Logging logs](/application-integration/docs/cloud-logging).\n\nWhat's next\n-----------\n\n- Learn how to [monitor you integrations using Cloud Monitoring](/application-integration/docs/cloud-monitoring)\n- Learn how to [create alerts](/application-integration/docs/alerts)"]]
