Google Distributed Cloud (GDC) 에어 갭은 애플리케이션과 서비스를 효과적으로 관리하는 데 도움이 되는 운영 로깅 기능을 제공합니다. 운영 로그는 배포 내에서 발생하는 조건, 변경사항, 작업에 관한 정보를 캡처하므로 개발자와 운영자는 다음 작업을 할 수 있습니다.
문제 해결: 애플리케이션 및 인프라에서 오류 또는 예상치 못한 동작을 식별하고 진단합니다.
성능 모니터링: 리소스 사용량을 추적하고, 시스템 이벤트 기록을 유지하고, 애플리케이션 성능을 최적화합니다.
이 섹션에서는 운영 로그를 이해하고 쿼리하는 데 도움이 됩니다. 운영 로그를 검색하기 위해 LogQL (로그 쿼리 언어) 표현식을 구성할 때 이 섹션을 참고하세요. 자세한 내용은 로그 쿼리 및 보기를 참고하세요.
[[["이해하기 쉬움","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-09-05(UTC)"],[[["\u003cp\u003eGoogle Distributed Cloud (GDC) air-gapped offers operational logging to help manage applications and services, capturing information about conditions, changes, and actions within deployments.\u003c/p\u003e\n"],["\u003cp\u003eOperational logs enable developers and operators to troubleshoot issues by identifying and diagnosing errors or unexpected behavior.\u003c/p\u003e\n"],["\u003cp\u003eOperational logs can be used to monitor performance by tracking resource usage, maintaining records of system events, and optimizing application performance.\u003c/p\u003e\n"],["\u003cp\u003eGDC collects operational logs for various resources, including Kubernetes workloads from the standard output (\u003ccode\u003estdout\u003c/code\u003e) and standard error (\u003ccode\u003estderr\u003c/code\u003e) streams of applications.\u003c/p\u003e\n"]]],[],null,["# Operational logs overview\n\nGoogle Distributed Cloud (GDC) air-gapped provides operational logging capabilities to help\nyou manage your applications and services effectively. Operational logs capture\ninformation about the conditions, changes, and actions occurring within your\ndeployments, letting developers and operators do the following:\n\n- **Troubleshoot issues**: Identify and diagnose errors or unexpected behavior in your applications and infrastructure.\n- **Monitor performance**: Track resource usage, maintain a record of system events, and optimize application performance.\n\nThis section helps to understand and query operational logs. Use this section\nfor reference when constructing\n[LogQL](https://grafana.com/docs/loki/latest/logql/) (Log Query Language)\nexpressions to search for operational logs. For more information, see\n[Query and view logs](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/query-and-view-logs).\n\nGDC collects operational logs for various resources,\nincluding the following:\n\n- **Kubernetes workloads** : Logs are captured from the standard output (`stdout`) and standard error (`stderr`) streams of your applications, adhering to the Kubernetes Container Runtime Interface (CRI) logging format. This practice ensures consistency and compatibility with Kubernetes' logging tools and practices. For more information on this format, refer to the official Kubernetes documentation: \u003chttps://github.com/kubernetes/design-proposals-archive/blob/main/node/kubelet-cri-logging.md\u003e."]]
