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
Cloud Logging
application associated with your Google Cloud 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-07 UTC."],[[["This document pertains to version 1.9 of the Apigee hybrid documentation, which includes services that output operational log information for troubleshooting."],["Apigee hybrid services in Kubernetes clusters generate log data crucial for debugging issues, and support teams may request this information for problem diagnosis."],["Each runtime plane service writes logs to stdout/stderr, which Kubernetes then stores on the host filesystem, where a log collector then exports them to Cloud Logging."],["The logs collector is a DaemonSet that runs on each hybrid node to gather log data."]]],[]]
