[[["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-08-26 UTC."],[[["\u003cp\u003eLogs can be viewed using the Logs Explorer in the Google Cloud console or directly via the \u003ccode\u003ekubectl logs\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIn GKE and GKE on-prem, logging is enabled by default, whereas in AKS you must explicitly enable logging.\u003c/p\u003e\n"],["\u003cp\u003eTo view logs in the Logs Explorer, navigate to the Logs Explorer in the Google Cloud console and select "Kubernetes Container," your cluster name, and namespace ID.\u003c/p\u003e\n"],["\u003cp\u003eYou can directly view log files by running the command \u003ccode\u003ekubectl logs pod_name -n namespace\u003c/code\u003e within your terminal.\u003c/p\u003e\n"]]],[],null,["# View logs\n\n| You are currently viewing version 1.13 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis topic explains how to\n[view log data](/logging/docs/view/logs-explorer-interface) by\nusing the Logs Explorer in the Google Cloud console or by using the\n`kubectl logs` command.\n| **Note:** Ingress logs are managed through Cloud Service Mesh. To view access logs, refer to [Accessing\n| logs in Cloud Logging](/service-mesh/v1.12/docs/observability/accessing-logs) in the Cloud Service Mesh documentation.\n\nView logs in the Logs Explorer\n------------------------------\n\n\nThis section explains how to view Apigee hybrid logs in the Logs Explorer or directly by using\n`kubectl`.\n| 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.\n\nIf you are on GKE on Google Cloud or on-premises as part of Google Distributed Cloud, logs are automatically sent to\n[Cloud Logging](/monitoring/kubernetes-engine).\n\n**To view logs in the Logs Explorer:**\n\n1. In the Google Cloud console, go to the **Logs Explorer** page.\n\n [Go to the Logs Explorer](https://console.cloud.google.com/logs/query)\n2. In the **Resource type** drop-down list, select\n **Kubernetes Container**, the\n name of your cluster, and your namespace ID.\n\n For more information, see\n [View\n logs](/logging/docs/view/overview) in the Google Cloud console documentation.\n\nThe following example shows hybrid log output in the Logs Explorer:\n\nView log files directly\n-----------------------\n\nYou can view the logs that are written to each pod's filesystem\ndirectly using [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/), as follows: \n\n```\nkubectl logs pod_name -n namespace\n```\n\nFor example: \n\n```text\nkubectl logs apigee-mp-hybrid-docs-test-blue-6fb96f5b9-2k8hp -n my-namespace\n```"]]
