디버그는 Apigee에서 실행되는 API 프록시 문제를 해결하고 모니터링할 수 있는 도구입니다. 디버그 도구를 사용하면 API 프록시 흐름을 통해 각 단계의 세부정보를 프로브할 수 있습니다.
Apigee를 사용하면 API 프록시의 전체 요청/응답 흐름을 보여주는 디버그 데이터를 수집할 수 있습니다. 여기에는 모든 요청/응답 매개변수와 정책 실행 시간에 적용된 변환이 포함됩니다. 이는 API 프록시 개발 및 배포 시 디버깅 및 문제 해결에 중요합니다.
디버그 데이터 수집 및 전송
Apigee 게이트웨이 노드는 디버그 세션 데이터를 수집하고 내부적으로 캐시한 후 Cloud의 컨트롤 플레인으로 데이터를 전송합니다. 그런 다음 운영자가 분석할 수 있도록 디버그 세션 UI에 공유됩니다.
마스킹 디버그를 사용하는 경우 Apigee는 디버그 데이터를 컨트롤 플레인으로 전송하기 전에 게이트웨이 노드에서 마스킹을 실행합니다.
디버그 사용
디버그 사용에 설명된 대로 UI 또는 API를 사용하여 디버그 도구로 디버그 세션을 만들고 관리합니다.
또는 오프라인 디버그 사용에 설명된 대로 디버그 세션을 다운로드하고 오프라인으로 보고 분석할 수 있습니다.
Apigee 디버그 지원 사용
고객만 디버그 세션을 트리거할 수 있지만 Apigee 지원팀은 지원 케이스 중에 삭제되지 않은 이전 디버그 세션에 액세스하여 프록시 관련 문제를 해결할 수 있습니다.
다음에 유의하세요.
Apigee 지원팀은 디버그 데이터에 대한 읽기 전용 권한을 가집니다.
Apigee 지원팀에서는 디버그를 실행하여 문제에 대한 정보를 캡처하고 지원팀에서 캡처된 디버그를 검토할 수 있도록 디버그 세션 ID 또는 디버그 세션 링크를 제공하도록 요청할 수 있습니다. 저장된 디버그 세션은 24시간 동안만 유효하므로 디버그 세션을 다운로드하고 지원팀에서 열어놓은 케이스에 연결하여 오프라인 보기를 사용 설정하는 것이 좋습니다.
[[["이해하기 쉬움","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-08-01(UTC)"],[[["\u003cp\u003eThe Debug tool in Apigee and Apigee hybrid allows users to troubleshoot and monitor API proxies by providing detailed insights into each step of an API proxy flow.\u003c/p\u003e\n"],["\u003cp\u003eDebug data, which captures the entire request/response flow and transformations, is crucial for debugging during API proxy development and deployment.\u003c/p\u003e\n"],["\u003cp\u003eApigee Support can access past debug sessions to assist in troubleshooting proxy issues, although they have read-only permissions.\u003c/p\u003e\n"],["\u003cp\u003eFor Apigee hybrid v1.13.1 and later, the Debug tool is supported for new organizations with data residency enabled.\u003c/p\u003e\n"],["\u003cp\u003eDebug data is not available in real-time, and is saved for 24 hours.\u003c/p\u003e\n"]]],[],null,["# Debug overview\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n| **Note:** For Apigee hybrid v1.13.1, the new data pipeline is supported for newly created Apigee hybrid organizations with [data residency](/apigee/docs/api-platform/get-started/drz-concepts) enabled. See [Configure hybrid to use the new data pipeline](/apigee/docs/hybrid/v1.13/data-collection-with-data-residency). For Hybrid 1.14 or later, the new data pipeline is the default for all Hybrid organizations regardless of whether or not data residency is enabled.\n\nDebug is a tool for troubleshooting and monitoring API proxies running on Apigee. The Debug tool\nlets you probe the details of each step\nthrough an API proxy flow.\nApigee lets you collect debug data, which shows the entire request/response flow of your\nAPI proxies. This includes all request/response parameters along with transformations applied to\nthem at policy execution time. This is important for debugging and troubleshooting during API proxy development and deployment.\n| In previous versions of Apigee, the Debug tool was referred to as the Trace tool.\n| **Terminology:** The terms *debug data* and *debug\n| session data* are used interchangeably.\n\nDebug data collection and transmission\n--------------------------------------\n\nApigee gateway nodes collect debug session data and cache it internally,\nbefore transmitting that data to the control plane in the Cloud. From there it\nis shared to the debug session UI, for operators to analyze.\n\nIf you use [Debug masking](/apigee/docs/api-platform/security/data-masking),\nApigee performs the masking in the gateway nodes, before transmitting the debug data to the\ncontrol plane.\n\nUsing Debug\n-----------\n\n\nCreate and manage debug sessions using the Debug tool using the UI or API, as described in\n[Using Debug](/apigee/docs/api-platform/debug/trace).\nAlternatively, you can download debug sessions and view and analyze them offline, as described in\n[Using Offline Debug](/apigee/docs/api-platform/debug/offline-trace).\n\nApigee Support use of Debug\n---------------------------\n\n\nOnly customers can trigger a debug session, but Apigee Support can access non-deleted past debug sessions\nduring the course of a support case to help troubleshoot proxy-specific issues.\n\n\nNote the following:\n\n- Apigee Support has read-only permission to Debug data.\n- Apigee Support may request that you run a debug to capture information about an issue, and that you provide the debug session ID or a link to the debug session so that Support may review the captured debug. Since saved debug sessions are valid for only 24 hours, we recommend that you download the debug session and attach it to the case opened with Support to enable offline viewing.\n\nFor Apigee hybrid users\n-----------------------\n\n| **Note:** For Apigee hybrid v1.13.1 and later, the Debug tool is supported for newly created Apigee hybrid organizations with [data residency](/apigee/docs/api-platform/get-started/drz-concepts) enabled. See [Analytics and debug data collection with data residency](/apigee/docs/hybrid/v1.13/data-collection-with-data-residency).\n\n\nIf you are using Apigee hybrid, review the following sections.\n\n### Debug architecture\n\nThe following illustrates the process of creating a new debug session:\n\n| **Note:** Because of the asynchronous nature of multiple pollings, debug data is not available in real time; instead, there is a slight delay.\n\nDebug data is persisted in the management plane for up to 24 hours.\n\n### Apigee hybrid requirements\n\nThis section lists important information for Apigee hybrid users.\n\n#### Support for data residency\n\n- If you have a newly created Apigee hybrid v1.13.1 org with [data residency enabled](/apigee/docs/api-platform/get-started/drz-concepts), follow the steps in [Using data residency with Apigee hybrid](/apigee/docs/hybrid/v1.13/using-data-residency-with-apigee-hybrid).\n- Clocks on all Synchronizer nodes should be in sync and in UTC.\n\nOlder versions of Apigee hybrid do not support data residency.\n\n#### Other requirements\n\n- You must have the `apigee-udca` service account configured. See [Specify configuration overrides](./install-create-overrides#specify-configuration-overrides).\n- Clocks on all Synchronizer nodes should be in sync and in UTC."]]
