Debug adalah alat untuk memecahkan masalah dan memantau proxy API yang berjalan di Apigee. Alat Debug
memungkinkan Anda memeriksa detail setiap langkah
melalui alur proxy API.
Apigee memungkinkan Anda mengumpulkan data debug, yang menunjukkan seluruh alur permintaan/respons proxy API Anda. Hal ini mencakup semua parameter permintaan/respons beserta transformasi yang diterapkan padanya pada waktu eksekusi kebijakan. Hal ini penting untuk proses debug dan pemecahan masalah selama pengembangan dan deployment proxy API.
Men-debug pengumpulan dan transmisi data
Node gateway Apigee mengumpulkan data sesi debug dan menyimpannya dalam cache secara internal,
sebelum mengirimkan data tersebut ke bidang kontrol di Cloud. Dari sana, data tersebut dibagikan ke UI sesi debug, untuk dianalisis oleh operator.
Jika Anda menggunakan Penyamaran debug,
Apigee melakukan penyamaran di node gateway, sebelum mengirimkan data debug ke
bidang kontrol.
Menggunakan Debug
Buat dan kelola sesi debug menggunakan alat Debug melalui UI atau API, seperti yang dijelaskan dalam
Menggunakan Debug.
Atau, Anda dapat mendownload sesi debug dan melihat serta menganalisisnya secara offline, seperti yang dijelaskan dalam
Menggunakan Debug Offline.
Penggunaan Debug oleh Dukungan Apigee
Hanya pelanggan yang dapat memicu sesi debug, tetapi Dukungan Apigee dapat mengakses sesi debug sebelumnya yang tidak dihapus
selama proses kasus dukungan untuk membantu memecahkan masalah khusus proxy.
Perhatikan hal berikut:
Dukungan Apigee memiliki izin hanya baca untuk data Debug.
Dukungan Apigee dapat meminta Anda menjalankan debug untuk mengambil informasi tentang masalah, dan Anda memberikan ID sesi debug atau link ke sesi debug sehingga Dukungan dapat meninjau debug yang diambil. Karena sesi debug tersimpan hanya berlaku selama
24 jam, sebaiknya download sesi debug dan lampirkan ke
kasus yang dibuka dengan Dukungan untuk mengaktifkan tampilan offline.
Untuk pengguna Apigee Hybrid
Jika Anda menggunakan Apigee hybrid, tinjau bagian berikut.
Arsitektur debug
Berikut ini mengilustrasikan proses pembuatan sesi debug baru:
Data debug dipertahankan di bidang pengelolaan hingga 24 jam.
Persyaratan Apigee Hybrid
Bagian ini mencantumkan informasi penting bagi pengguna Apigee Hybrid.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 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."]]
