Metrics Cardinality Control and Relabeling

By Michael Samuel Naeem · June 11, 2026 · 6 min read

Prometheus TSDB 2TB from unbounded path label on HTTP metrics. This post is about making metrics cardinality control and relabeling boring in the best way — predictable under load, auditable under review, and reversible under stress.

Scenario worth designing for

Prometheus TSDB 2TB from unbounded path label on HTTP metrics.

Hard constraints

Compliance, latency, and cost caps are constraints — not afterthoughts. Design for rollback and audit evidence from day one.

Implementation walkthrough

Ship the smallest production slice of Metrics Cardinality Control and Relabeling: one pipeline, one cluster, or one namespace — with rollback documented before widening scope.

Automate the boring steps so on-call never hand-edits cardinality control settings during an incident. GitOps, versioned checkpoints, and pinned module versions beat runbook heroics.

How we validate before promote

Integration tests with production-shaped data volumes. Chaos or fault injection for dependency timeouts.

Replay one bad day of production traffic in staging before declaring cardinality control done.

Production hardening

Pin versions, restrict break-glass access, and align client timeouts with server queue delays.

Review on-call pages tied to this topic after every incident — even minor ones.

Closing thought

Good metrics cardinality control and relabeling work is invisible until it saves you from an outage, an audit finding, or a line item on the cloud bill.

Reference configuration

# Operational hook for cardinality control
@task(retries=3, retry_delay=timedelta(minutes=5))
def run_metrics_cardinality_control():
    validate_preconditions()
    execute()
    emit_lineage(run_id=ctx.run_id)

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Operating cardinality control at scale

After the first successful deploy of metrics cardinality control and relabeling, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of cardinality control settings with the on-call rotation — not only the primary author.

Handoff to adjacent teams

Observability pipelines touch ingestion, serving, and finance. Document interfaces where cardinality control gates hand off to downstream owners so failures are not bounced without context.

Further reading

• https://opentelemetry.io/docs/