[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-08-30(UTC)"],[[["\u003cp\u003eThis documentation pertains to Apigee hybrid version 1.6, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid logs can be viewed on Stackdriver for GKE and GKE on-prem, and logging must be explicitly enabled for AKS.\u003c/p\u003e\n"],["\u003cp\u003eOn GKE or Anthos GKE, logs are automatically sent to Stackdriver, accessible via the Monitoring Logs Viewer.\u003c/p\u003e\n"],["\u003cp\u003eLogs written to each pod's filesystem can also be viewed directly using the \u003ccode\u003ekubectl logs\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIngress logs are managed through Anthos Service Mesh (ASM) and can be accessed via Cloud Logging, as explained in the ASM documentation.\u003c/p\u003e\n"]]],[],null,["# View logs\n\n| You are currently viewing version 1.6 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis topic explains how to view log data on\n[Stackdriver](https://cloud.google.com/monitoring/kubernetes-engine/) and using the `kubectl logs`\ncommand.\n| **Note:** Ingress logs are managed through Anthos Service Mesh (ASM). To view access logs, refer to [Accessing\n| logs in Cloud Logging](/service-mesh/v1.12/docs/observability/accessing-logs) in the ASM documentation.\n\nView logs on Stackdriver\n------------------------\n\n\nThis section explains how to view Apigee hybrid logs on Stackdriver and directly 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 or Anthos GKE, logs are automatically sent to\n[Stackdriver](https://cloud.google.com/monitoring/kubernetes-engine/).\n\n**To view logs on Stackdriver:**\n\n1. Go to [Monitoring Logs Viewer](https://console.cloud.google.com/logs/viewer?_ga=2.139334906.-813617201.1555966039).\n2. In the resource-type drop-down list, select GKE Container, the name of your cluster, and your namespace ID. For example: \n\n For more information, see\n [Viewing\n logs](https://cloud.google.com/logging/docs/view/overview) in the Google Cloud documentation.\n\nThe following example shows hybrid log output in the Log viewer:\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```"]]
