Difference between revisions of "GKE logs"
Jump to navigation
Jump to search
(3 intermediate revisions by 2 users not shown) | |||
Line 9: | Line 9: | ||
− | + | * <code>[[GCP Node logs]]</code> | |
− | + | * <code>[[gcloud logging read]]</code> | |
+ | |||
+ | |||
+ | * [[Cluster logs]] | ||
+ | * [[Autoscaler logs]] | ||
+ | |||
+ | == Related == | ||
+ | * [[Fluentbit]]: https://cloud.google.com/stackdriver/docs/solutions/gke/managing-logs#custom_agents | ||
+ | * <code>[[fluent-bit-gke-exporter]]</code> | ||
== See also == | == See also == |
Latest revision as of 09:31, 29 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,
Related[edit]
- Fluentbit: https://cloud.google.com/stackdriver/docs/solutions/gke/managing-logs#custom_agents
fluent-bit-gke-exporter
See also[edit]
Advertising: