View logs

You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, seeSupported versions.

This topic explains how toview log data by using the Logs Explorer in the Google Cloud console or by using thekubectl logs command.

Note: Ingress logs are managed through Cloud Service Mesh. To view access logs, refer toAccessing logs in Cloud Logging in the Cloud Service Mesh documentation.

View logs in the Logs Explorer

This section explains how to view Apigee hybrid logs in the Logs Explorer or directly by usingkubectl.

Logging is provided by default on GKE and GKE on-prem. On theseplatforms, be sure that you have disabled logging in your overrides file by settinglogger.enabled tofalse. On AKS, you must explicitly enablelogging by settinglogger.enabled totrue in your overrides file.

If you are on GKE on Google Cloud or on-premises as part of Google Distributed Cloud, logs are automatically sent toCloud Logging.

To view logs in the Logs Explorer:

  1. In the Google Cloud console, go to theLogs Explorer page.

    Go to the Logs Explorer

  2. In theResource type drop-down list, selectKubernetes Container, the name of your cluster, and your namespace ID.

    For more information, seeView logs in the Google Cloud console documentation.

The following example shows hybrid log output in the Logs Explorer:

View log files directly

You can view the logs that are written to each pod's filesystemdirectly usingkubectl, as follows:

kubectl logspod_name -nnamespace

For example:

kubectl logs apigee-mp-hybrid-docs-test-blue-6fb96f5b9-2k8hp -n my-namespace

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.