감사 로그를 탭합니다.감사 로그를 사용하면 통합 내에서 누가, 언제, 어디서, 무엇을 했는지 파악할 수 있습니다. 이러한 로그는 Cloud Logging에서만 볼 수 있으며 로그에서 발생하는 추가 요금은 없습니다.
Application Integration을 사용하면 Cloud Logging에 실행 로그를 저장하여 이러한 로그에 대한 알림 및 커스텀 보관을 설정하는 등 Cloud Logging 기능을 활용할 수 있습니다.
Application Integration 로그
통합을 실행하면 해당 통합에 대해 실행 로그가 생성되고 통합을 만든 리전에 저장됩니다. 이러한 로그에 액세스하여 오류를 해결하고 통합의 각 단계 상태를 확인할 수 있습니다.
다음 이미지는 실행 로그 페이지를 보여줍니다.
Application Integration에서 로그를 보는 방법에 대한 자세한 내용은 통합 실행 로그를 참조하세요.
Cloud Logging
Cloud Logging은 스토리지, 검색, 분석, 모니터링 지원을 갖춘 실시간 로그 관리 시스템입니다. Application Integration을 사용하면 Cloud Logging 기능을 활용할 수 있습니다. 기본적으로 Cloud Logging은 통합에 대해 사용 중지됩니다. 통합의 게시되지 않은 버전을 수정하여 통합에 로깅을 사용 설정할 수 있습니다.
Cloud Logging은 다음과 같은 심각도 수준의 통합 런타임 로그를 캡처합니다.
정보: 모든 통합 실행(SUCCEEDED, FAILED, PROCESSING, PENDING, SUSPENDED, CANCELLED)과 관련된 실행 로그 및 기타 세부정보가 포함된 로그입니다.
오류 및 경고:FAILED 및 CANCELLED 통합 실행 상태와 관련된 실행 로그 및 기타 세부정보가 포함된 로그입니다.
Application Integration 로그에는 추가 비용이 들지 않지만 감사 로그와 Cloud Logging에는 서로 다른 가격 책정 모델이 적용됩니다.
Cloud Logging 가격 책정에 대한 자세한 내용은 Cloud Logging 가격 책정을 참조하세요.
제한사항
통합 로그에는 다음과 같은 제한사항이 적용됩니다.
Cloud Logging은 최대 256KiB 크기의 로그 항목만 지원합니다. 로그가 이 한도를 초과하면 요청 및 응답 매개변수가 로깅 세부정보에 표시되지 않습니다. Cloud Logging 할당량 및 한도에 대한 자세한 내용은 할당량 및 한도를 참조하세요. 이 오류를 해결하려면 값이 한도를 초과하지 않도록 통합 변수의 값을 수정합니다. 또는 Application Integration에서 이러한 로그를 확인할 수도 있습니다. 이 제한은 Cloud Logging 로그에 적용됩니다.
로컬 로깅이 중지되어 있으면 Cloud Logging이 사용 설정되어 있더라도 실행 로그가 Cloud Logging으로 전송되지 않습니다. 이 제한사항은 통합 실행 로그 및 Cloud Logging 로그 모두에 적용됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(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)"]]