Metric | Type | Description |
apiserver_request_duration_seconds_bucket | Histogram | The latency between a request sent to kube-apiserver and a response returned by kube-apiserver. Requests are classified based on the following dimensions: Verb: the type of the request, such as GET, POST, PUT, and DELETE. Group: the API group, which contains related API operations used to extend the Kubernetes API. Version: the API version, such as v1 and v1beta1. Resource: the type of the resource that the request is sent to access, such as pod, Service, and lease. Subresource: the subresources of the resource, such as pod details and pod logs. Scope: the scope of the request, such as resources in a namespace or resources in a cluster. Component: the name of the component that initiates the request, such as kube-controller-manager, kube-scheduler, or cloud-controller-manager. Client: the client that sends the request, which may be an internal component or an external service.
The buckets in the histogram of kube-scheduler include 0.05, 0.1, 0.15, 0.2, 0.25, 0.3, 0.35, 0.4, 0.45, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 1.25, 1.5, 1.75, 2.0, 2.5, 3.0, 3.5, 4.0, 4.5, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 40, 50, and 60 . Unit: seconds. |
apiserver_request_total | Counter | The number of different requests received by kube-apiserver. Requests are classified based on verbs, groups, versions, resource, scope, component, HTTP content types, HTTP status code, and clients. |
apiserver_request_no_resourceversion_list_total | Counter | The number of LIST requests that are sent to kube-apiserver and for which the resourceVersion parameter is not specified. This metric is used to check whether an excessive number of LIST requests of the quorum read type are sent to kube-apiserver and locate the client that sends such requests. This can help optimize client behavior and improve cluster performance. Requests are classified based on groups, versions, resources, scopes, and clients. |
apiserver_current_inflight_requests | Gauge | The number of requests that are being processed by kube-apiserver. Requests are classified into the following types: ReadOnly: This type of requests does not change the status of clusters. In most cases, this type of requests is sent to read resources in clusters, such as querying pods and querying node status. Mutating: This type of requests changes the status of clusters. In most cases, this type of requests is sent to create, update, or delete resources, such as creating a pod or updating the configurations of a Service.
|
apiserver_dropped_requests_total | Counter | The number of requests that are dropped when throttling is performed on kube-apiserver. A request is dropped if the 429 'Try again later' HTTP status code is returned. |
etcd_request_duration_seconds_bucket | Histogram | The latency between a request sent from kube-apiserver and a response returned by etcd. Requests are classified based on operations and operation types. The buckets in the histogram include 0.005, 0.025, 0.05, 0.1, 0.2, 0.4, 0.6, 0.8, 1.0, 1.25, 1.5, 2, 3, 4, 5, 6, 8, 10, 15, 20, 30, 45, and 60 . Unit: seconds. |
apiserver_admission_controller_admission_duration_seconds_bucket | Gauge | The processing latency of the admission controller. The histogram is identified by the admission controller name, operation such as CREATE, UPDATE, or CONNECT, API resource, operation type such as validate or admit, and whether the request is denied. The buckets of the histogram include 0.005, 0.025, 0.1, 0.5, and 2.5 . Unit: seconds. |
apiserver_admission_webhook_admission_duration_seconds_bucket | Gauge | The processing latency of the admission webhook. The histogram is identified by the admission controller name, operation such as CREATE, UPDATE, or CONNECT, API resource, operation type such as validate or admit, and whether the request is denied. The buckets of the histogram include 0.005, 0.025, 0.1, 0.5, and 2.5 . Unit: seconds. |
apiserver_admission_webhook_admission_duration_seconds_count | Counter | The number of requests processed by the admission webhook. The histogram is identified by the admission controller name, operation such as CREATE, UPDATE, or CONNECT, API resource, operation type such as validate or admit, and whether the request is denied. |
cpu_utilization_core | Gauge | The number of used CPU cores. Unit: cores. |
memory_utilization_byte | Gauge | The amount of used memory. Unit: bytes. |
up | Gauge | Indicates whether kube-apiserver is available. |