All of the Apigee hybrid services that run in your Kubernetes
cluster output operational log information. This log information is
useful for troubleshooting and debugging. For example, if a service
pod's status indicates a problem, you can look at the log files for
that pod to gain insight into the issue. Apigee support may request
you to provide log information to diagnose and solve a problem.
About logging
Each runtime plane service writes log data to stdout/stderr, and
Kubernetes writes this data to the host filesystem. A logs
collector for hybrid runs on each hybrid node. The
collector is a DaemonSet (replicated once and only once per node) whose job
is to collect the written log data and export it to the
Stackdriver Logging
application associated with your GCP account.
The following diagram shows the log data collection process:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis documentation version (1.4) for Apigee hybrid is end-of-life and an upgrade to a newer version is required.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid services within the Kubernetes cluster generate operational logs useful for troubleshooting and debugging.\u003c/p\u003e\n"],["\u003cp\u003eEach runtime plane service writes log data to stdout/stderr, which is collected and exported to Stackdriver Logging by a logs collector.\u003c/p\u003e\n"],["\u003cp\u003eThe log collector operates as a DaemonSet, running once per node in the cluster.\u003c/p\u003e\n"]]],[],null,["# Logging overview\n\n| You are currently viewing version 1.4 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\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.4/access-logs)\n- [View logs](/apigee/docs/hybrid/v1.4/logging-view)"]]
