[[["이해하기 쉬움","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-03-12(UTC)"],[[["This document explains how to view Apigee hybrid log data using the Logs Explorer in the Google Cloud console or the `kubectl logs` command."],["Ingress logs are managed through Anthos Service Mesh (ASM), and access logs can be viewed in Cloud Logging per the ASM documentation."],["Logging is provided by default on GKE and GKE on-prem, and on AKS you must explicitly enable logging by setting `logger.enabled` to `true`."],["Logs can be viewed in the Logs Explorer by selecting **Kubernetes Container** under **Resource type**, along with the cluster name and namespace ID."],["You can also view logs directly from the pod's filesystem by using the `kubectl logs pod_name -n namespace` command."]]],[]]