NOTE: Some aspects of this product are in Beta. The hybrid installation options are GA. To join the Beta program, reach out to your Apigee representative.

Logging overview

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:

alt_text

Next steps