이 문서에서는 Application Integration에 통합 실행 로그가 저장되는 방식과 통합에 로컬 로깅을 사용 설정하는 방법을 설명합니다.
개요
로컬 로깅은 실행 중에 저장된 통합 데이터나 메타데이터를 나타냅니다. Application Integration은 저장된 데이터를 사용하여 통합 실행 로그를 생성합니다.
로컬 로깅을 다음 세 가지 모드 중 하나로 설정할 수 있습니다.
사용 설정(동기화): 통합이 실행되는 동안 로그 데이터가 유지(쓰기)됩니다. 이 모드에서 Application Integration은 각 실행 단계 후에 로그 데이터를 동기식으로 작성합니다. 이 모드는 모든 통합 실행의 로그를 생성합니다.
우선순위에 로그 생성이 보장되고 통합 실행 시간의 지연이 허용되는 경우 이 모드를 사용하세요.
사용 설정(비동기): 기본적으로 통합의 로컬 로깅은 비동기 모드로 사용 설정됩니다.
로그 데이터는 고정된 간격으로나 통합 실행이 완료된 후(둘 중 더 빠른 시점)에 유지(쓰기)됩니다. 이 모드에서는 Enable(sync) 모드에 비해 통합 실행 시간이 상대적으로 덜 걸립니다. Application Integration에서 통합 실행 중에 로그 데이터를 비동기적으로 쓰기 때문입니다. 하지만 이 모드는 모든 실행에 대한 로그 생성을 보장하지는 않습니다. 드문 경우지만 통합 실행에 대해 로그가 생성되지 않을 수 있습니다.
지연 시간을 줄이면서 통합을 실행하는 것이 우선이며 보장된 로그 생성이 비교적 덜 중요한 경우 이 모드를 사용하세요.
사용 중지: 통합 실행 로그가 생성되지 않습니다. 로컬 로깅을 중지하면 요청 및 응답 매개변수, 기타 통합 변수의 로그 이벤트가 생성되지 않으므로 전반적으로 통합 지연 시간이 단축됩니다.
[[["이해하기 쉬움","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-06-16(UTC)"],[[["\u003cp\u003eThis document outlines how Application Integration saves integration execution logs and how to enable local logging for integrations.\u003c/p\u003e\n"],["\u003cp\u003eLocal logging can be set to three modes: \u003ccode\u003eEnable(sync)\u003c/code\u003e for guaranteed log generation, \u003ccode\u003eEnable(async)\u003c/code\u003e for reduced latency, or \u003ccode\u003eDisable\u003c/code\u003e for the best integration latency, but no logs.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eEnable(sync)\u003c/code\u003e mode writes log data synchronously after each step, ensuring log generation, while \u003ccode\u003eEnable(async)\u003c/code\u003e writes data asynchronously, potentially missing some logs.\u003c/p\u003e\n"],["\u003cp\u003eLocal logging settings can be configured within the integration editor by accessing the settings menu and selecting the desired mode from the "Local logging" dropdown.\u003c/p\u003e\n"],["\u003cp\u003eIntegration execution logs are retained for 90 days by default; however, the retention period can be modified by enabling Cloud Logging and setting a new retention period for the project.\u003c/p\u003e\n"]]],[],null,["# Local logging\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nLocal logging\n=============\n\nThis document describes how integration execution logs are saved in Application Integration and how to enable local logging for your integrations.\n\nOverview\n--------\n\nLocal logging refers to the integration's data or metadata that is saved during its execution. Application Integration\nuses the saved data to generate the [integration execution logs](/application-integration/docs/integration-execution-logs).\n\nYou can set the **Local logging** to any of the following three modes:\n\n- **Enable(sync):** The log data is persisted (written) during integration's execution. In this mode, Application Integration writes the log data synchronously after each execution step. This mode guarantees the generation of logs for all the integration executions.\n\n Use this mode if your priority is to have a guaranteed generation of logs, and a latency in\n integration execution time is acceptable.\n- **Enable(async):** By default, local logging for an integration is enabled in async mode. The log data is persisted (written) at fixed intervals or after the completion of the integration's execution, whichever is earlier. In this mode, the integration takes a relatively lesser time to execute when compared to `Enable(sync)` mode, because Application Integration writes the log data asynchronously during the integration execution. However, this mode doesn't guarantee the generation of logs for all the executions. In rare cases, it's possible that logs aren't generated for an integration execution.\n\n Use this mode if your priority is to run your integrations with reduced latency, and the guaranteed\n generation of logs is relatively of a lesser importance.\n- **Disable:** The execution logs aren't generated for the integration. Disabling the local logging improves the overall integration latency, as log events aren't generated for request and response parameters, and other integration variables.\n\nConfigure local logging\n-----------------------\n\nTo configure the local logging for your integration, do the following steps:\n\n1. Open your integration in the [integration editor](/application-integration/docs/integrations-ui-layout).\n2. In the toolbar, click **settingsIntegration settings**.\n3. From the **Local logging** list, select the [local logging mode](#overview). By default, **Local logging** is set to **Enable(async)**.\n4. Click **Done**.\n\n| **Tip:**Disabling the local logging improves the overall integration latency, as log events aren't generated for request and response parameters, and other integration variables.\n\nRetention period\n----------------\n\nThe retention period for integration execution logs is 90 days. If you want to modify the retention period, you must enable Cloud Logging and configure the retention period for your project. For more information, see [Logging retention](/logging/docs/routing/overview#logs-retention).\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- Learn about [all tasks and triggers](/application-integration/docs/all-triggers-tasks).\n- Learn how to [test and publish an integration](/application-integration/docs/test-publish-integrations).\n\n- Learn about [error handling](/application-integration/docs/error-handling-strategy).\n- Learn about [integration execution logs](/application-integration/docs/introduction-logs)."]]
