| title | linkTitle | weight | description |
|---|---|---|---|
Metrics |
Metrics |
7 |
Inspect Karpenter Metrics
|
Karpenter makes several metrics available in Prometheus format to allow monitoring cluster provisioning status. These metrics are available by default at karpenter.karpenter.svc.cluster.local:8000/metrics configurable via the METRICS_PORT environment variable documented here
Number of currently used workers per controller
Maximum number of concurrent reconciles per controller
Total number of reconciliation errors per controller
Length of time per reconciliation per controller
Total number of reconciliations per controller
Number of consistency checks that have failed.
Number of deprovisioning actions performed. Labeled by deprovisioner.
Number of times the Consolidation algorithm has reached a timeout. Labeled by consolidation type.
Number of machines eligible for deprovisioning by Karpenter. Labeled by deprovisioner
Duration of the deprovisioning evaluation process in seconds.
Amount of time required for a replacement machine to become initialized.
The number of times that Karpenter failed to launch a replacement node for deprovisioning. Labeled by deprovisioner.
Number of disruption actions performed. Labeled by disruption method.
Number of times the Consolidation algorithm has reached a timeout. Labeled by consolidation type.
Number of nodes eligible for disruption by Karpenter. Labeled by disruption method.
Duration of the disruption evaluation process in seconds.
The number of times that Karpenter failed to launch a replacement node for disruption. Labeled by disruption method.
Amount of time required for a replacement nodeclaim to become initialized.
Number of notification actions performed. Labeled by action
Count of messages deleted from the SQS queue.
Length of time between message creation in queue and an action taken on the message by the controller.
Count of messages received from the SQS queue. Broken down by message type and whether the message was actionable.
Number of machines created in total by Karpenter. Labeled by reason the machine was created and the owning provisioner.
Number of machines disrupted in total by Karpenter. Labeled by disruption type of the machine and the owning provisioner.
Number of machine drifted reasons in total by Karpenter. Labeled by drift type of the machine and the owning provisioner..
Number of machines initialized in total by Karpenter. Labeled by the owning provisioner.
Number of machines launched in total by Karpenter. Labeled by the owning provisioner.
Number of machines registered in total by Karpenter. Labeled by the owning provisioner.
Number of machines terminated in total by Karpenter. Labeled by reason the machine was terminated and the owning provisioner.
Number of nodeclaims created in total by Karpenter. Labeled by reason the nodeclaim was created and the owning nodepool.
Number of nodeclaims disrupted in total by Karpenter. Labeled by disruption type of the nodeclaim and the owning nodepool.
Number of nodeclaims drifted reasons in total by Karpenter. Labeled by drift type of the nodeclaim and the owning nodepool.
Number of nodeclaims initialized in total by Karpenter. Labeled by the owning nodepool.
Number of nodeclaims launched in total by Karpenter. Labeled by the owning nodepool.
Number of nodeclaims registered in total by Karpenter. Labeled by the owning nodepool.
Number of nodeclaims terminated in total by Karpenter. Labeled by reason the nodeclaim was terminated and the owning nodepool.
The nodepool limits are the limits specified on the provisioner that restrict the quantity of resources provisioned. Labeled by nodepool name and resource type.
The nodepool usage is the amount of resources that have been provisioned by a particular nodepool. Labeled by nodepool name and resource type.
The Provisioner Limits are the limits specified on the provisioner that restrict the quantity of resources provisioned. Labeled by provisioner name and resource type.
Duration of scheduling process in seconds.
Duration of scheduling simulations used for deprovisioning and provisioning in seconds.
The Provisioner Usage is the amount of resources that have been provisioned by a particular provisioner. Labeled by provisioner name and resource type.
The Provisioner Usage Percentage is the percentage of each resource used based on the resources provisioned and the limits that have been configured in the range [0,100]. Labeled by provisioner name and resource type.
Node allocatable are the resources allocatable by nodes.
Number of nodes created in total by Karpenter. Labeled by owning provisioner.
Number of deleted leaked leases.
Node system daemon overhead are the resources reserved for system overhead, the difference between the node's capacity and allocatable values are reported by the status.
Number of nodes terminated in total by Karpenter. Labeled by owning provisioner.
The time taken between a node's deletion request and the removal of its finalizer
Node total daemon limits are the resources specified by DaemonSet pod limits.
Node total daemon requests are the resource requested by DaemonSet pods bound to nodes.
Node total pod limits are the resources specified by non-DaemonSet pod limits.
Node total pod requests are the resources requested by non-DaemonSet pods bound to nodes.
The time from pod creation until the pod is running.
Pod state is the current state of pods. This metric can be used several ways as it is labeled by the pod name, namespace, owner, node, provisioner name, zone, architecture, capacity type, instance type and pod phase.
Duration of cloud provider method calls. Labeled by the controller, method name and provider.
Total number of errors returned from CloudProvider calls.
VCPUs cores for a given instance type.
Memory, in bytes, for a given instance type.
Estimated hourly price used when making informed decisions on node cost calculation. This is updated once on startup and then every 12 hours.
Size of the request batch per batcher
Duration of the batching window per batcher