Back to guidesGuide

Debug Prometheus relabeling when targets disappear without creating cardinality spikes

A practical workflow for using the relabeling visualizer, isolating risky rules, and proving that important telemetry still exists.

Fix Prometheus relabeling rules that remove useful targets or keep unstable labels, without breaking alerts or inflating the TSDB.

Created: June 14, 2026

Published: June 14, 2026

Estimated time40 min
LevelIntermediate
Before you startRead access to Prometheus and its configuration
PlatformsLinux
WhatsAppXLinkedIn

Linux

Validate configuration, query active/dropped targets, and measure cardinality before and after the change.

promtoolcurljqHTTP access to Prometheus
Validate configuration
promtool check config prometheus.yml
Inspect active targets
curl -s http://prometheus:9090/api/v1/targets?state=active | jq '.data.activeTargets | length'
Measure cardinality pressure
curl -s http://prometheus:9090/api/v1/status/tsdb | jq '.data.headStats'

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.