# Budget Prometheus label values before adding high-cardinality dimensions

> Every distinct label set creates another time series with real operating cost.

- Canonical URL: https://update.dsesecurity.com/updates/budget-prometheus-label-values-before-adding-high-cardinality-dimensions/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-20T18:15:43+00:00
- Modified: 2026-10-20T18:34:33+00:00
- Last reviewed by DSE: 2026-10-20
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Every distinct label set creates another time series with real operating cost.

## Potentially affected

Review labelset cardinality and instrumentation cost using Prometheus's general design guidance.

## DSE recommendation

DSE recommends estimating the possible combinations before adding a label, including growth and values generated by retries or user input.

## Article

Every distinct label set creates another time series with real operating cost.

## Source facts

Prometheus instrumentation guidance states that each label set adds a time series with memory, CPU, disk and network costs. Large numbers of metrics and label combinations can accumulate quickly. It recommends limiting cardinality and considering other analysis systems when the potential population becomes large.

Source: [Prometheus documentation — Instrumentation](https://prometheus.io/docs/practices/instrumentation/).

## Applicability

Review labelset cardinality and instrumentation cost using Prometheus’s general design guidance.

## DSE recommendation

DSE recommends estimating the possible combinations before adding a label, including growth and values generated by retries or user input. Keep request identifiers, unrestricted paths, and other effectively unbounded data out of metric dimensions unless a reviewed design justifies them. Use logs or traces where per-event detail is the actual requirement. Assign an owner to the metric’s label contract and review changes during application releases. Preserve the operational question the metric answers so cost reduction does not remove essential diagnostic meaning.

## Verification

In a representative test workload, inspect the resulting series count and distinct values for each proposed label. Compare the observed population with the estimate and exercise an unusual input path. Confirm instrumentation cannot create uncontrolled new values before enabling the dimension across the full production fleet. Retain the proposed value domains and resulting series count with the workload profile. Ask the instrumentation owner to demonstrate the agreed bound under unusual inputs before accepting the label contract across more instances.

## Official reference

[Prometheus documentation — Instrumentation](https://prometheus.io/docs/practices/instrumentation/). Reviewed October 20, 2026.

## Primary reference

- Name: Prometheus documentation — Instrumentation
- Authority: prometheus.io
- URL: https://prometheus.io/docs/practices/instrumentation/
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Budget Prometheus label values before adding high-cardinality dimensions,” DSE Security, https://update.dsesecurity.com/updates/budget-prometheus-label-values-before-adding-high-cardinality-dimensions/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.