Observability Guides
EspañolEnglish
← Back to guidesGuide

Reducing Prometheus cardinality spikes without breaking alerts

Practical steps to find explosive series, limit labels and validate impact in production

A hands-on guide to detect high-cardinality sources, apply safe relabeling and rollups, and confirm critical alerts remain effective.

Created: April 11, 2026

Published: April 11, 2026

Estimated time60 min
LevelAdvanced
Before you startAccess to Prometheus (web UI and API)
PlatformsDocker / Linux
WhatsAppXLinkedIn

Docker

Safe Docker commands to inspect Prometheus and reload configuration without destructive actions.

Docker CLI able to list and exec into containersprometheus.yml mounted from host or accessible inside container
List Prometheus containers
docker ps --filter "ancestor=prom/prometheus" --format "{{.ID}} {{.Names}} {{.Status}}"
Count matching series via API
docker exec -i <prometheus_container> curl -sS "http://localhost:9090/api/v1/series?match[]=up" | jq 'length'
Tail Prometheus logs (safe)
docker logs --since 1h <prometheus_container> --tail 200
Reload config without restart
docker exec -i <prometheus_container> curl -sS -X POST http://localhost:9090/-/reload
Also available inReducir picos de cardinalidad en Prometheus sin romper alertas

Content locked

This guide requires both steps before full content is available.

  • ○Click “Like” on this guide.
  • ○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.