Difference between revisions of "GKE logs"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
[[gcloud logging read]] | [[gcloud logging read]] | ||
| + | |||
| + | == Related == | ||
| + | * [[Fluentbit]]: https://cloud.google.com/stackdriver/docs/solutions/gke/managing-logs#custom_agents | ||
== See also == | == See also == | ||
Revision as of 11:29, 20 September 2022
- https://cloud.google.com/stackdriver/docs/solutions/gke/managing-logs
- https://cloud.google.com/stackdriver/docs/solutions/gke/using-logs
- GKE container logs are removed when their host Pod is removed, when the disk on which they are stored runs out of space, or when they are replaced by newer logs.
- System logs are periodically removed to free up space for new logs.
- Cluster events are removed after one hour.
GKE deploys, by default a per-node logging agent that reads container logs, adds helpful metadata, and then stores logs for container and system logs,
GCP Node logs
gcloud logging read
Related
See also
Advertising:
