kubernetes metrics options
- 1 minutes read - 179 wordsComponents |
Description |
Metrics |
Scaler |
Metrics Server |
Metrics Server collects resource metrics from Kubelets and exposes them in Kubernetes apiserver through Metrics API for use by Horizontal Pod Autoscaler and Vertical Pod Autoscaler. Metrics API can also be accessed by kubectl top, making it easier to debug autoscaling pipelines. Metrics Server is not meant for non-autoscaling purposes |
CPU/Memory |
|
cAdvisor |
an open-source agent integrated into the kubelet binary that monitors resource usage and analyzes the performance of containers. It collects statistics about the CPU, memory, file, and network usage for all containers running on a given node (it does not operate at the pod level). |
CPU, memory, file, and network usage for all containers |
|
kube-state-metrics |
kube-state-metrics (KSM) is a simple service that listens to the Kubernetes API server and generates metrics about the state of the objects. (See examples in the Metrics section below.) It is not focused on the health of the individual Kubernetes components, but rather on the health of the various objects inside, such as deployments, nodes and pods. |
||
Kubernetes API Server |
|||
Node Exporter, |
|||
KEDA metric server |
|||
prometheus-adapter |