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-03-10 UTC."],[[["The current Apigee hybrid documentation version (1.3) is end-of-life and users are advised to upgrade to a newer version."],["Apigee hybrid services in Kubernetes clusters generate operational logs for troubleshooting and debugging, which Apigee support may request."],["Each runtime plane service logs data to stdout/stderr, with Kubernetes storing this data on the host filesystem, which is then collected by a DaemonSet log collector."],["The collected log data is exported to Stackdriver Logging, the application associated with the user's GCP account."]]],[]]
