Metrics & Infrastructure
Resource Saturation
Updated Jul 28, 2026 · 1d ago
A resource pinned near its limit — CPU, memory, disk, connection pool — long enough to matter, not a momentary touch.
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
Watches saturation-class metric series and fires only on sustained high utilization, not single-sample spikes. Understands polarity — for available/free/idle metrics it inverts, so low free memory is read as high saturation. Absolute floors keep tiny resources from paging.
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.
- Slow Drift
The boiling-frog leak: a metric trending steadily the wrong way over hours, too gradual for any spike alarm to catch.
- Metric Reporting Gap
A metric series that simply stopped arriving — a dead exporter, a broken scrape, a crashed agent — where the absence is the alert.
- 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.