Metrics & Infrastructure

Metric Peer Outlier

Updated Oct 24, 2026 · today

Raises warnings when a metric stays worse for one instance than for comparable peers through the latest complete interval.

Example alert

Warning: worker-12 queue depth remains above comparable workers through the last complete minute.

Exact wording varies — the detector generates titles from the anomaly it finds. This is representative of what an alert looks like when it fires.

Runs on these tiers:

TrialTeamGrowthCustom

Want to see this detector firing in the live demo?

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.
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.