From 1bb431a6a2653b795ca2beb514042ce45cc22257 Mon Sep 17 00:00:00 2001 From: David Martin Date: Mon, 22 Apr 2024 11:44:10 +0100 Subject: [PATCH] Update doc/observability/metrics.md Co-authored-by: Jason Madigan <4467+jasonmadigan@users.noreply.github.com> --- doc/observability/metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/observability/metrics.md b/doc/observability/metrics.md index 520255640..53de2e6db 100644 --- a/doc/observability/metrics.md +++ b/doc/observability/metrics.md @@ -21,7 +21,7 @@ and how to join the metrics from different sources together in a meaningful way. Resource metrics, like CPU, memory and disk usage, primarily come from the Kubernetes metrics components. These include `container_cpu_usage_seconds_total`, `container_memory_working_set_bytes` and `kubelet_volume_stats_used_bytes`. A [stable list of metrics](https://github.com/kubernetes/kubernetes/blob/master/test/instrumentation/testdata/stable-metrics-list.yaml) is maintained in -the kubernetes repository. These low level metrics typically have a set of +the kubernetes repository. These low-level metrics typically have a set of [recording rules](https://prometheus.io/docs/practices/rules/#aggregation) that aggregate values by labels and time ranges. For example, `node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate` or `namespace_workload_pod:kube_pod_owner:relabel`.