diff --git a/content/en/docs/reference/instrumentation/metrics.md b/content/en/docs/reference/instrumentation/metrics.md index 0cc90d8d78..4b5ae9fc9a 100644 --- a/content/en/docs/reference/instrumentation/metrics.md +++ b/content/en/docs/reference/instrumentation/metrics.md @@ -6,16 +6,16 @@ description: >- Details of the metric data that Kubernetes components export. --- -## Metrics (v1.27) +## Metrics (v1.28) - - + + This page details the metrics that different Kubernetes components export. You can query the metrics endpoint for these components using an HTTP scrape, and fetch the current metrics data in Prometheus format. ### List of Stable Kubernetes Metrics -Stable metrics observe strict API contracts and no labels can be added or removed from stable metrics during their lifetime. +Stable metrics observe strict API contracts and no labels can be added or removed from stable metrics during their lifetime.
apiserver_flowcontrol_current_executing_requests | +BETA | +Gauge | +Number of requests in initial (for a WATCH) or any (for a non-WATCH) execution stage in the API Priority and Fairness subsystem | +flow_schema priority_level |
++ | |
apiserver_flowcontrol_current_executing_seats | +BETA | +Gauge | +Concurrency (number of seats) occupied by the currently executing (initial stage for a WATCH, any stage otherwise) requests in the API Priority and Fairness subsystem | +flow_schema priority_level |
++ | |
apiserver_flowcontrol_current_inqueue_requests | +BETA | +Gauge | +Number of requests currently pending in queues of the API Priority and Fairness subsystem | +flow_schema priority_level |
++ | |
apiserver_flowcontrol_dispatched_requests_total | +BETA | +Counter | +Number of requests executed by API Priority and Fairness subsystem | +flow_schema priority_level |
++ | |
apiserver_flowcontrol_nominal_limit_seats | +BETA | +Gauge | +Nominal number of execution seats configured for each priority level | +priority_level |
++ | |
apiserver_flowcontrol_rejected_requests_total | +BETA | +Counter | +Number of requests rejected by API Priority and Fairness subsystem | +flow_schema priority_level reason |
++ | |
apiserver_flowcontrol_request_wait_duration_seconds | +BETA | +Histogram | +Length of time a request spent waiting in its queue | +execute flow_schema priority_level |
++ | |
disabled_metrics_total | +BETA | +Counter | +The count of disabled metrics. | ++ | + | |
hidden_metrics_total | +BETA | +Counter | +The count of hidden metrics. | ++ | + | |
kubernetes_feature_enabled | +BETA | +Gauge | +This metric records the data about the stage and enablement of a k8s feature. | +name stage |
++ | |
kubernetes_healthcheck | +BETA | +Gauge | +This metric records the result of a single healthcheck. | +name type |
++ | |
kubernetes_healthchecks_total | +BETA | +Counter | +This metric records the results of all healthcheck. | +name status type |
++ | |
registered_metrics_total | +BETA | +Counter | +The count of registered metrics broken by stability level and deprecation version. | +deprecated_version stability_level |
++ |
crd group reason version |
- | ||||||||
apiserver_admission_admission_match_condition_evaluation_errors_total | +|||||||||
apiserver_admission_match_condition_evaluation_errors_total | ALPHA | Counter | -Admission match condition evaluation errors count, identified by name of resource containing the match condition and broken out for each admission type (validating or mutating). | -name type |
+Admission match condition evaluation errors count, identified by name of resource containing the match condition and broken out for each kind containing matchConditions (webhook or policy), operation and admission type (validate or admit). | +kind name operation type |
++ | ||
apiserver_admission_match_condition_evaluation_seconds | +ALPHA | +Histogram | +Admission match condition evaluation time in seconds, identified by name and broken out for each kind containing matchConditions (webhook or policy), operation and type (validate or admit). | +kind name operation type |
++ | ||||
apiserver_admission_match_condition_exclusions_total | +ALPHA | +Counter | +Admission match condition evaluation exclusions count, identified by name of resource containing the match condition and broken out for each kind containing matchConditions (webhook or policy), operation and admission type (validate or admit). | +kind name operation type |
|||||
apiserver_admission_step_admission_duration_seconds_summary | @@ -431,7 +535,21 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||||
apiserver_crd_webhook_conversion_duration_seconds | +|||||||||
apiserver_conversion_webhook_duration_seconds | +ALPHA | +Histogram | +Conversion webhook request latency | +failure_type result |
++ | ||||
apiserver_conversion_webhook_request_total | +ALPHA | +Counter | +Counter for conversion webhook requests with success/failure and failure error type | +failure_type result |
++ | ||||
apiserver_crd_conversion_webhook_duration_seconds | ALPHA | Histogram | CRD webhook conversion duration in seconds | @@ -494,6 +612,27 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourprotocol transport |
|||||
apiserver_encryption_config_controller_automatic_reload_failures_total | +ALPHA | +Counter | +Total number of failed automatic reloads of encryption configuration. | ++ | + | ||||
apiserver_encryption_config_controller_automatic_reload_last_timestamp_seconds | +ALPHA | +Gauge | +Timestamp of the last successful or failed automatic reload of encryption configuration. | +status |
++ | ||||
apiserver_encryption_config_controller_automatic_reload_success_total | +ALPHA | +Counter | +Total number of successful automatic reloads of encryption configuration. | ++ | + | ||||
apiserver_envelope_encryption_dek_cache_fill_percent | ALPHA | Gauge | @@ -543,20 +682,6 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourgrpc_status_code method_name provider_name |
||||||
apiserver_flowcontrol_current_executing_requests | -ALPHA | -Gauge | -Number of requests in initial (for a WATCH) or any (for a non-WATCH) execution stage in the API Priority and Fairness subsystem | -flow_schema priority_level |
-- | ||||
apiserver_flowcontrol_current_inqueue_requests | -ALPHA | -Gauge | -Number of requests currently pending in queues of the API Priority and Fairness subsystem | -flow_schema priority_level |
-- | ||||
apiserver_flowcontrol_current_limit_seats | ALPHA | Gauge | @@ -613,13 +738,6 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourpriority_level |
||||||
apiserver_flowcontrol_dispatched_requests_total | -ALPHA | -Counter | -Number of requests executed by API Priority and Fairness subsystem | -flow_schema priority_level |
-- | ||||
apiserver_flowcontrol_epoch_advance_total | ALPHA | Counter | @@ -655,13 +773,6 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourbound priority_level |
||||||
apiserver_flowcontrol_nominal_limit_seats | -ALPHA | -Gauge | -Nominal number of execution seats configured for each priority level | -priority_level |
-- | ||||
apiserver_flowcontrol_priority_level_request_utilization | ALPHA | TimingRatioHistogram | @@ -683,27 +794,20 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourphase request_kind |
||||||
apiserver_flowcontrol_rejected_requests_total | -ALPHA | -Counter | -Number of requests rejected by API Priority and Fairness subsystem | -flow_schema priority_level reason |
-- | ||||
apiserver_flowcontrol_request_concurrency_in_use | ALPHA | Gauge | Concurrency (number of seats) occupied by the currently executing (initial stage for a WATCH, any stage otherwise) requests in the API Priority and Fairness subsystem | flow_schema priority_level |
- | 1.31.0 | |||
apiserver_flowcontrol_request_concurrency_limit | ALPHA | Gauge | -Shared concurrency limit in the API Priority and Fairness subsystem | +Nominal number of execution seats configured for each priority level | priority_level |
- | 1.30.0 | ||
apiserver_flowcontrol_request_dispatch_no_accommodation_total | ALPHA | Counter | @@ -725,13 +829,6 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourflow_schema priority_level |
||||||
apiserver_flowcontrol_request_wait_duration_seconds | -ALPHA | -Histogram | -Length of time a request spent waiting in its queue | -execute flow_schema priority_level |
-- | ||||
apiserver_flowcontrol_seat_fair_frac | ALPHA | Gauge | @@ -844,6 +941,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourcode_path |
||||||
apiserver_rerouted_request_total | +ALPHA | +Counter | +Total number of requests that were proxied to a peer kube apiserver because the local apiserver was not capable of serving it | +code |
++ | ||||
apiserver_selfrequest_total | ALPHA | Counter | @@ -871,7 +975,7 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourTotal size of the storage database file physically allocated in bytes. | endpoint |
- | 1.28.0 | |||
apiserver_storage_decode_errors_total | ALPHA | Counter | @@ -921,6 +1025,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourresource |
||||||
apiserver_storage_size_bytes | +ALPHA | +Custom | +Size of the storage database file physically allocated in bytes. | +cluster |
++ | ||||
apiserver_storage_transformation_duration_seconds | ALPHA | Histogram | @@ -931,7 +1042,7 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||
apiserver_storage_transformation_operations_total | ALPHA | Counter | -Total number of transformations. | +Total number of transformations. Successful transformation will have a status 'OK' and a varied status string when the transformation fails. This status and transformation_type fields may be used for alerting on encryption/decryption failure using transformation_type from_storage for decryption and to_storage for encryption | status transformation_type transformer_prefix |
- | |||
attachdetach_controller_forced_detaches | +|||||||||
attach_detach_controller_attachdetach_controller_forced_detaches | ALPHA | Counter | Number of times the A/D Controller performed a forced detach | -+ | reason |
||||
attachdetach_controller_total_volumes | @@ -1082,6 +1193,20 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourstatus |
||||||||
authorization_attempts_total | +ALPHA | +Counter | +Counter of authorization attempts broken down by result. It can be either 'allowed', 'denied', 'no-opinion' or 'error'. | +result |
++ | ||||
authorization_duration_seconds | +ALPHA | +Histogram | +Authorization duration in seconds broken out by result. | +result |
++ | ||||
cloud_provider_webhook_request_duration_seconds | ALPHA | Histogram | @@ -1208,6 +1333,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourcontainer pod namespace |
||||||
container_swap_usage_bytes | +ALPHA | +Custom | +Current amount of the container swap usage in bytes. Reported only on non-windows systems | +container pod namespace |
++ | ||||
csi_operations_seconds | ALPHA | Histogram | @@ -1369,6 +1501,20 @@ Alpha metrics do not have any API guarantees. These metrics must be used at youroperation type |
||||||
etcd_request_errors_total | +ALPHA | +Counter | +Etcd failed request counts for each operation and object type. | +operation type |
++ | ||||
etcd_requests_total | +ALPHA | +Counter | +Etcd request counts for each operation and object type. | +operation type |
++ | ||||
etcd_version_info | ALPHA | Gauge | @@ -1495,20 +1641,6 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||
kube_apiserver_nodeport_allocator_allocation_errors_total | -ALPHA | -Counter | -Number of errors trying to allocate NodePort | -scope |
-- | ||||
kube_apiserver_nodeport_allocator_allocation_total | -ALPHA | -Counter | -Number of NodePort allocations | -scope |
-- | ||||
kube_apiserver_nodeport_allocator_available_ports | ALPHA | Gauge | @@ -1967,14 +2099,14 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||
kubelet_started_host_process_containers_errors_total | ALPHA | Counter | -Cumulative number of errors when starting hostprocess containers. This metric will only be collected on Windows and requires WindowsHostProcessContainers feature gate to be enabled. | +Cumulative number of errors when starting hostprocess containers. This metric will only be collected on Windows. | code container_type |
||||
kubelet_started_host_process_containers_total | ALPHA | Counter | -Cumulative number of hostprocess containers started. This metric will only be collected on Windows and requires WindowsHostProcessContainers feature gate to be enabled. | +Cumulative number of hostprocess containers started. This metric will only be collected on Windows. | container_type |
+ | |||
kubeproxy_proxy_healthz_total | +ALPHA | +Counter | +Cumulative proxy healthz HTTP status | +code |
++ | ||||
kubeproxy_proxy_livez_total | +ALPHA | +Counter | +Cumulative proxy livez HTTP status | +code |
++ | ||||
kubeproxy_sync_full_proxy_rules_duration_seconds | +ALPHA | +Histogram | +SyncProxyRules latency in seconds for full resyncs | ++ | + | ||||
kubeproxy_sync_partial_proxy_rules_duration_seconds | +ALPHA | +Histogram | +SyncProxyRules latency in seconds for partial resyncs | ++ | + | ||||
kubeproxy_sync_proxy_rules_duration_seconds | ALPHA | Histogram | @@ -2104,6 +2264,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||
kubeproxy_sync_proxy_rules_iptables_last | +ALPHA | +Gauge | +Number of iptables rules written by kube-proxy in last sync | +table |
++ | ||||
kubeproxy_sync_proxy_rules_iptables_partial_restore_failures_total | ALPHA | Counter | @@ -2121,7 +2288,7 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||
kubeproxy_sync_proxy_rules_iptables_total | ALPHA | Gauge | -Number of proxy iptables rules programmed | +Total number of iptables rules owned by kube-proxy | table |
build_date compiler git_commit git_tree_state git_version go_version major minor platform |
- | ||
kubernetes_feature_enabled | -ALPHA | -Gauge | -This metric records the data about the stage and enablement of a k8s feature. | -name stage |
-- | ||||
kubernetes_healthcheck | -ALPHA | -Gauge | -This metric records the result of a single healthcheck. | -name type |
-- | ||||
kubernetes_healthchecks_total | -ALPHA | -Counter | -This metric records the results of all healthcheck. | -name status type |
-- | ||||
leader_election_master_status | ALPHA | Gauge | @@ -2237,6 +2383,20 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourzone |
||||||
node_controller_cloud_provider_taint_removal_delay_seconds | +ALPHA | +Histogram | +Number of seconds after node creation when NodeController removed the cloud-provider taint of a single node. | ++ | + | ||||
node_controller_initial_node_sync_delay_seconds | +ALPHA | +Histogram | +Number of seconds after node creation when NodeController finished the initial synchronization of a single node. | ++ | + | ||||
node_cpu_usage_seconds_total | ALPHA | Custom | @@ -2321,6 +2481,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||
node_swap_usage_bytes | +ALPHA | +Custom | +Current swap usage of the node in bytes. Reported only on non-windows systems | ++ | + | ||||
number_of_l4_ilbs | ALPHA | Gauge | @@ -2346,14 +2513,14 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourALPHA | Counter | Number of errors encountered when forcefully deleting the pods since the Pod GC Controller started. | -+ | namespace reason |
||
pod_gc_collector_force_delete_pods_total | ALPHA | Counter | Number of pods that are being forcefully deleted since the Pod GC Controller started. | -+ | namespace reason |
||||
pod_memory_working_set_bytes | @@ -2384,6 +2551,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourrequest_operation resource subresource |
||||||||
pod_swap_usage_bytes | +ALPHA | +Custom | +Current amount of the pod swap usage in bytes. Reported only on non-windows systems | +pod namespace |
++ | ||||
prober_probe_duration_seconds | ALPHA | Histogram | @@ -2468,6 +2642,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your|||||||
rest_client_dns_resolution_duration_seconds | +ALPHA | +Histogram | +DNS resolver latency in seconds. Broken down by host. | +host |
++ | ||||
rest_client_exec_plugin_call_total | ALPHA | Counter | @@ -2531,6 +2712,20 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourhost verb |
||||||
rest_client_transport_cache_entries | +ALPHA | +Gauge | +Number of transport entries in the internal cache. | ++ | + | ||||
rest_client_transport_create_calls_total | +ALPHA | +Counter | +Number of calls to get a new transport, partitioned by the result of the operation hit: obtained from the cache, miss: created and added to the cache, uncacheable: created and not cached | +result |
++ | ||||
retroactive_storageclass_errors_total | ALPHA | Counter | @@ -2601,13 +2796,6 @@ Alpha metrics do not have any API guarantees. These metrics must be used at yourtype |
||||||
scheduler_scheduler_goroutines | -ALPHA | -Gauge | -Number of running goroutines split by the work they do such as binding. This metric is replaced by the \"goroutines\" metric. | -work |
-- | 1.26.0 | |||
scheduler_scheduling_algorithm_duration_seconds | ALPHA | Histogram |