Semua layanan Apigee hybrid yang berjalan di cluster Kubernetes Anda akan menghasilkan informasi log operasional. Informasi log ini berguna untuk pemecahan masalah dan proses debug. Misalnya, jika status pod layanan menunjukkan adanya masalah, Anda dapat melihat file log untuk pod tersebut guna mendapatkan insight tentang masalah tersebut. Dukungan Apigee dapat meminta Anda untuk memberikan informasi log guna mendiagnosis dan menyelesaikan masalah.
Tentang logging
Setiap layanan platform runtime menulis data log ke stdout/stderr, dan
Kubernetes menulis data ini ke sistem file host. Pengumpul log untuk hybrid berjalan di setiap node hybrid. Pengumpul adalah DaemonSet (direplikasi sekali dan hanya sekali per node) yang tugasnya mengumpulkan data log yang ditulis dan mengekspornya ke aplikasi Stackdriver Logging yang terkait dengan akun GCP Anda.
Diagram berikut menunjukkan proses pengumpulan data log:
[[["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-04 UTC."],[[["\u003cp\u003eApigee hybrid documentation version 1.1 is end of life and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid services running in Kubernetes clusters generate operational logs that are valuable for troubleshooting and debugging purposes.\u003c/p\u003e\n"],["\u003cp\u003eEach runtime plane service logs to stdout/stderr, which Kubernetes then writes to the host filesystem, and a dedicated collector on each node then exports the logs.\u003c/p\u003e\n"],["\u003cp\u003eThe log collector, a DaemonSet, gathers log data and exports it to Stackdriver Logging in the associated GCP account.\u003c/p\u003e\n"]]],[],null,["# Logging overview\n\n| You are currently viewing version 1.1 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nAll of the Apigee hybrid services that run in your Kubernetes\ncluster output operational log information. This log information is\nuseful for troubleshooting and debugging. For example, if a service\npod's status indicates a problem, you can look at the log files for\nthat pod to gain insight into the issue. Apigee support may request\nyou to provide log information to diagnose and solve a problem.\n\nAbout logging\n-------------\n\nEach runtime plane service writes log data to stdout/stderr, and\nKubernetes writes this data to the host filesystem. A logs\ncollector for hybrid runs on each hybrid node. The\ncollector is a [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) (replicated once and only once per node) whose job it\nis to collect the written log data and export it to the\n[Stackdriver Logging](https://cloud.google.com/logging/docs/)\napplication associated with your GCP account.\n\nThe following diagram shows the log data collection process:\n\nNext steps\n----------\n\n- [Enable access logs](/apigee/docs/hybrid/v1.1/access-logs)\n- [View logs](/apigee/docs/hybrid/v1.1/logging-view)"]]
