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.