View logs

You are currently viewing version 1.10 of the Apigee hybrid documentation. For more information, see Supported versions.

Version 1.10 

   Supported versions:

• v1.14 (latest)                        
• v1.13                         
• v1.12                         
• v1.11                         
• List of supported versions

   Unsupported versions:

• v1.10                                      
• v1.9                                         
• v1.8                                         
• v1.7                                         
• v1.6                                         
• v1.5                                         
• v1.4                                         
• v1.3                                         
• v1.2                                         
• v1.1                                         

This topic explains how to view log data by using the Logs Explorer in the Google Cloud console or by using the kubectl logs command.

Note: Ingress logs are managed through Anthos Service Mesh (ASM). To view access logs, refer to Accessing logs in Cloud Logging in the ASM documentation.

View logs in the Logs Explorer

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

Logging is provided by default on GKE and GKE on-prem. On these platforms, be sure that you have disabled logging in your overrides file by setting logger.enabled to false. On AKS, you must explicitly enable logging by setting logger.enabled to true in your overrides file.

If you are on GKE or Anthos GKE, logs are automatically sent to Cloud Logging.

To view logs in the Logs Explorer:

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

   Go to the Logs Explorer

2. In the Resource type drop-down list, select Kubernetes Container, the name of your cluster, and your namespace ID.

   For more information, see View 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 filesystem directly using kubectl, as follows:

kubectl logs pod_name -n namespace

For example:

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