Difference between revisions of "Monitoring Kubernetes"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
== Related == | == Related == | ||
| − | * [[Kubernetes node conditions]] | + | * [[Kubernetes events]]: [[Kubernetes node conditions]] |
* <code>[[Pod The node had condition:]]</code> | * <code>[[Pod The node had condition:]]</code> | ||
* [[Container]]: <code>[[is approaching memory limit]]</code> ([[Datadog]]) | * [[Container]]: <code>[[is approaching memory limit]]</code> ([[Datadog]]) | ||
Revision as of 07:26, 20 September 2023
https://kubernetes.io/docs/tasks/debug/debug-cluster/resource-usage-monitoring/
- Pixie (New Relic)
- Prometheus
- Kube-state-metrics (KSM):
helm install myprometheus prometheus-community/prometheus - LogicMonitor
- CKA: Understand how to monitor applications in Kubernetes
- K8s log collection:
fluentd, fluentbit, promtail, kubectl logs
Activities
- Read https://www.datadoghq.com/blog/monitoring-kubernetes-performance-metrics/#cluster-state-metrics
Related
- Kubernetes events: Kubernetes node conditions
Pod The node had condition:- Container:
is approaching memory limit(Datadog) - Prometheus, VictoriaMetrics, Grafana
node-problem-detectoraws-for-fluent-bitmonitoringnamespace- GKE: integrated logging and monitoring
- Kubernetes node-problem-detector
- Kubernetes troubleshooting
See also
Advertising:
