Difference between revisions of "Monitoring Kubernetes"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
* [[CKA]]: [[Understand how to monitor applications in Kubernetes]] | * [[CKA]]: [[Understand how to monitor applications in Kubernetes]] | ||
| − | * [[K8s log collection]]: [[fluentd]], [[fluentbit]], [[promtail]] | + | * [[K8s log collection]]: <code>[[fluentd]], [[fluentbit]], [[promtail]]</code> |
== Activities == | == Activities == | ||
Revision as of 08:03, 31 October 2022
- Pixie (New Relic)
- Prometheus
- Kube-state-metrics (KSM):
helm install myprometheus prometheus-community/prometheus
- CKA: Understand how to monitor applications in Kubernetes
- K8s log collection:
fluentd, fluentbit, promtail
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) - Prometheus, VictoriaMetrics, Grafana
node-problem-detectoraws-for-fluent-bitmonitoringnamespace- GKE: integrated logging and monitoring
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:
