Stay organized with collections
Save and categorize content based on your preferences.
Google Distributed Cloud (GDC) air-gapped provides operational logging capabilities to help
you manage your applications and services effectively. Operational logs capture
information about the conditions, changes, and actions occurring within your
deployments, letting developers and operators do the following:
Troubleshoot issues: Identify and diagnose errors or unexpected behavior
in your applications and infrastructure.
Monitor performance: Track resource usage, maintain a record of system
events, and optimize application performance.
This section helps to understand and query operational logs. Use this section
for reference when constructing
LogQL (Log Query Language)
expressions to search for operational logs. For more information, see
Query and view logs.
GDC collects operational logs for various resources,
including the following:
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:
https://github.com/kubernetes/design-proposals-archive/blob/main/node/kubelet-cri-logging.md.
[[["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-25 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."]]