Difference between revisions of "Monitoring Kubernetes"
Jump to navigation
Jump to search
| (19 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | https://kubernetes.io/docs/tasks/debug/debug-cluster/resource-usage-monitoring/ | |
* [[Pixie]] ([[New Relic]]) | * [[Pixie]] ([[New Relic]]) | ||
* [[Prometheus]] | * [[Prometheus]] | ||
* [[Kube-state-metrics (KSM)]]: <code>[[helm install myprometheus prometheus-community/prometheus]]</code> | * [[Kube-state-metrics (KSM)]]: <code>[[helm install myprometheus prometheus-community/prometheus]]</code> | ||
| + | * [[LogicMonitor]] | ||
* [[CKA]]: [[Understand how to monitor applications in Kubernetes]] | * [[CKA]]: [[Understand how to monitor applications in Kubernetes]] | ||
| − | * [[ | + | * [[K8s log collection]]: <code>[[fluentd]], [[fluentbit]], [[promtail]], [[kubectl logs]]</code> |
| + | |||
| + | * [[OpenMetrics]] ([[CNCF]]) | ||
| + | * [[EKS monitoring]]: [[AWS CloudWatch Container Insights]] | ||
| + | |||
| + | * [[Prometheus monitoring Mixin for Kubernetes]]: https://github.com/kubernetes-monitoring/kubernetes-mixin | ||
== Activities == | == Activities == | ||
| Line 12: | Line 18: | ||
== Related == | == Related == | ||
| − | * <code>[[kubectl | + | * [[Kubernetes events]]: <code>[[kubectl get events]]</code> |
* [[Kubernetes node conditions]] | * [[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]]) | ||
| − | * [[ | + | * [[Prometheus]], [[VictoriaMetrics]], [[Grafana]] |
| − | |||
| − | |||
* <code>[[node-problem-detector]]</code> | * <code>[[node-problem-detector]]</code> | ||
* <code>[[aws-for-fluent-bit]]</code> | * <code>[[aws-for-fluent-bit]]</code> | ||
* <code>[[monitoring]]</code> namespace | * <code>[[monitoring]]</code> namespace | ||
| + | * [[GKE]]: integrated [[logging]] and [[monitoring]] | ||
| + | * [[Kubernetes node-problem-detector]] | ||
| + | * [[Kubernetes troubleshooting]] | ||
| + | * <code>[[kubectl get svc -n monitoring]]</code> | ||
== See also == | == See also == | ||
| − | |||
* {{Kubernetes monitoring}} | * {{Kubernetes monitoring}} | ||
| − | |||
[[Category:Monitoring]] | [[Category:Monitoring]] | ||
[[Category:K8s]] | [[Category:K8s]] | ||
Latest revision as of 10:01, 1 December 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
- Prometheus monitoring Mixin for Kubernetes: https://github.com/kubernetes-monitoring/kubernetes-mixin
Activities[edit]
- Read https://www.datadoghq.com/blog/monitoring-kubernetes-performance-metrics/#cluster-state-metrics
Related[edit]
- 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[edit]
Advertising:
