[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Operational logs overview\n\nGoogle Distributed Cloud (GDC) air-gapped appliance 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/appliance/platform/pa-user/query-and-view-logs).\n\nGDC collects operational logs for various resources,\nincluding the following:\n\n- **Kubernetes pods** : 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."]]
