- Docs
- Observability
- Metrics
Metrics
Set up Prometheus, add app, node, and object metrics, read control-plane and component metrics, and keep them long term
- metrics-server and live usage metrics-server ships in every cluster and feeds kubectl top and the HorizontalPodAutoscaler, but it keeps only the latest sample, so it is not history.
- Set up Prometheus Install the Prometheus Operator and one Prometheus that only receives, because the Alloy collectors do all the scraping.
- Control-plane metrics etcd, kube-controller-manager, kube-scheduler, the kubelet, and KubeGate keep their metrics on loopback, and this page covers what each one tells you and how it is reached.
- Cluster object metrics with kube-state-metrics kube-state-metrics turns every Kubernetes object's state into a metric, including the custom NodeConditions the health daemon latches, so you can alert on them.
- Node and hardware metrics node-exporter binds to the host, so scrape it over loopback to get CPU, memory, disk, NVMe, and network metrics for cloud and bare-metal pools.
- Custom application metrics Expose your app's metrics and declare a ServiceMonitor or PodMonitor; the Application Alloy reads those objects, shards the targets across replicas, and keeps app cardinality away from node telemetry.
- Long-term storage and remote-write Prometheus local storage is short-lived, so remote-write to Thanos, Mimir, or Victoria Metrics for durable, queryable, multi-cluster history.
- Data-plane and cluster component metrics The platform's networking, DNS, storage, and cloud-integration cluster components each report their own metrics, some on loopback and some on the pod network, and this page covers what each one tells you.