Infrastructure Metric Rules

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

Evaluates threshold rules against specific named infrastructure metrics where the failure level is well known (Pending pods, consumer lag, replication lag, restart count). Ships conservatively — born capped at warning severity until validated, so it informs before it pages.

Availability

Runs on these tiers:

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.

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

• Host Liveness

  Flags a host or node that has stopped reporting, so a silent box surfaces as a warning rather than as missing data.