Difference between revisions of "Monitoring Kubernetes"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* [[Pixie]] ([[New Relic]]) | * [[Pixie]] ([[New Relic]]) | ||
* [[Prometheus]] | * [[Prometheus]] | ||
| − | * [[Kube-state-metrics (KSM)]] | + | * [[Kube-state-metrics (KSM)]]: <code>[[helm install myprometheus prometheus-community/prometheus]]</code> |
* [[CKA]]: [[Understand how to monitor applications in Kubernetes]] | * [[CKA]]: [[Understand how to monitor applications in Kubernetes]] | ||
Revision as of 12:06, 16 September 2022
- Pixie (New Relic)
- Prometheus
- Kube-state-metrics (KSM):
helm install myprometheus prometheus-community/prometheus
Activities
- Read https://www.datadoghq.com/blog/monitoring-kubernetes-performance-metrics/#cluster-state-metrics
Related
kubectl logs- Kubernetes node conditions
Pod The node had condition:- Container:
is approaching memory limit(Datadog) - promtail
- Grafana
- Prometheus
node-problem-detectoraws-for-fluent-bit
See also
- Monitoring: On call, Monitoring software, Monitoring services, Resource monitoring, Metric colletion tools, network monitoring, SLA Management Monitoring Tools, Alarm/Alert, Resource starvation, Alerts and notifications, Monitoring Kubernetes, VictoriaMetrics, Sensu, LogicMonitor, Distributed tracing
- Kubernetes monitoring, node conditions, Kube-state-metrics (KSM), Prometheus, VictoriaMetrics,
node-problem-detector, Thanos, log collection,ProbeWarning, Kubernetes node-problem-detector, Pixie, OpenMetrics,kind: PodMonitor, Jaeger
Advertising:
