Topic starter
19/08/2026 4:00 pm
TL;DR: Metric cardinality turns ordinary labels into a cost, performance, and availability problem across Prometheus-like stacks and SaaS monitoring platforms, according to Sawmills. The governance answer is not more dashboards, but label discipline, pipeline enforcement, and blast-radius controls that stop unbounded dimensions before they reach storage or billing.
Editorial analysis by NHI Mgmt Group, based on content published by Sawmills: “Why metric cardinality keeps exploding and how to tame it”.
Key questions
Q: What breaks when metric cardinality is not governed in observability pipelines?
A: When metric cardinality is not governed, series growth can overwhelm memory, indexing, query fanout, and recovery.
Q: Why do high-cardinality labels create cost and reliability problems?
A: High-cardinality labels multiply the number of time series that must be stored, indexed, queried, and billed.
Q: What are the signs that observability cardinality is getting out of control?
A: Common signs include sudden growth in active series, query fanout that slows dashboards, rising memory pressure, noisy alerts, and unexpected bill spikes.
Practitioner guidance
- Define a stable label allowlist Publish a short allowlist for metrics such as env, region, service, status_code, and method, then reject labels that introduce unbounded values like user_id, session, request_id, pod_uid, or raw URLs.
- Enforce label filtering before storage Use collectors, relabel rules, or pipeline controls to drop or rewrite risky dimensions before they reach the TSDB or SaaS index, because downstream dashboards cannot undo cardinality already ingested.
- Monitor series growth per service Track active series, series added per scrape, and sudden label-value spikes by service so that runaway metrics can be isolated to the owning workload instead of affecting the whole observability estate.
Bottom line: Metric cardinality becomes a governance failure when label combinations expand faster than teams can control cost, query load, and recovery behaviour.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:37 pm
Metric cardinality is an observability governance failure, not just a performance issue. Once label combinations are allowed to expand without policy, the monitoring stack loses predictability across cost, recovery, and query behaviour. The control problem is closer to identity inventory discipline than to dashboard tuning: you need rules for what may exist, where it may be attached, and how quickly it can be removed. The practitioner lesson is to treat telemetry shape as a governed asset.
A question worth separating out:
Q: Should teams rely on platform controls or pipeline controls for metric governance?
A: Pipeline controls should do most of the work because they can stop risky dimensions before storage or indexing. Platform controls are still useful for visibility and limits, but they are usually reactive. If the label reaches the backend, the cost and operational impact have already begun.
👉 Read our full editorial: Metric cardinality is breaking observability governance at scale