Metrics & Infrastructure
Metric Reporting Gap
Updated Jul 28, 2026 · 1d ago
A metric series that simply stopped arriving — a dead exporter, a broken scrape, a crashed agent — where the absence is the alert.
Example alert
Exact wording varies — the detector generates titles from the anomaly it finds. This is representative of what an alert looks like when it fires.
How it works
Tracks the expected reporting cadence of each metric series and fires when samples stop arriving for several expected intervals — the silent failure where a monitoring agent dies and the metric goes missing rather than going bad, which threshold alarms never see.
Availability
Runs on these tiers:
Want to see this detector firing in the live demo?
Open alerts in the sandbox →Related detectors
- Metric Anomaly
Spikes and dips in any numeric metric — CPU, memory, queue depth, request rate — against that metric's own seasonal baseline.
- Resource Saturation
A resource pinned near its limit — CPU, memory, disk, connection pool — long enough to matter, not a momentary touch.
- Slow Drift
The boiling-frog leak: a metric trending steadily the wrong way over hours, too gradual for any spike alarm to catch.
- Infrastructure Metric Rules
Named-metric guardrails: pods stuck Pending, consumer-group lag, replication lag, restart storms — metrics with a known-bad level.
- Host Liveness
Flags a host or node that has stopped reporting, so a silent box surfaces as a warning rather than as missing data.