Key Kubernetes Metrics That Actually Matter for Production Monitoring

A four-year production Kubernetes practitioner outlines a focused observability strategy across three distinct layers: cluster health, workload health, and application performance. Rather than tracking every available metric, the guidance emphasizes cluster-level capacity alerts over individual node CPU, and monitoring services instead of ephemeral pods. Critical signals include pod crash-loop detection, HPA scale-ceiling hits, and application-level error rates and latency using the RED and USE methods. A single four-panel dashboard covering capacity, workload status, error rates, and Kubernetes events is recommended to answer most operational questions quickly. Common pitfalls highlighted include ignoring the control plane, skipping resource requests, and alerting on raw resource usage instead of service-level objectives.