Difference between revisions of "Monitoring Kubernetes"
Jump to navigation
Jump to search
| Line 27: | Line 27: | ||
* [[Kubernetes node-problem-detector]] | * [[Kubernetes node-problem-detector]] | ||
* [[Kubernetes troubleshooting]] | * [[Kubernetes troubleshooting]] | ||
| + | * <code>[[kubectl get svc -n monitoring]]</code> | ||
== See also == | == See also == | ||
Revision as of 11:03, 30 November 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:
kubectl get 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
kubectl get svc -n monitoring
See also
Advertising:
