Paging Rules
Decide when to page, who to page, and how. Rules evaluate alert conditions and route to escalation policies or individuals.
Total Rules
7 enabled
Critical Rules
page immediately
Triggered (7d)
across all rules
Avg Per Rule
trigger rate
Paging Rules
Ordered top-to-bottom. First match wins.
Rule | Severity | Routes To | Triggered (7d) | Enabled | |
|---|---|---|---|---|---|
Tier-1 service degraded tier = 1 AND health = degraded | High | policyReliability - Standard | 4 | ||
Disk pressure warning metric = disk_usage AND value > 85 | Low | personu15 | 4 | ||
Checkout 5xx spike service = checkout-api AND metric = http_5xx_rate AND value > 1 | High | policyPlatform - Standard | 3 | ||
Critical production outage severity = critical AND environment = production | Critical | policyPlatform - Standard | 2 | ||
Kafka consumer lag spike service = kafka-bus AND metric = consumer_lag AND value > 50000 | Medium | policyPlatform - Standard | 1 | ||
After-hours billing queue service = billing-service AND queue_depth > 10000 AND hour NOT IN (9-17) | Medium | personu15 | 1 | ||
PostgreSQL replication lag service = postgres-primary AND metric = repl_lag AND value > 5 | High | policyReliability - Standard | 0 | ||
Security incident - vault service = vault AND category = security | Critical | policySecurity - Critical | 0 |
How Paging Works
From trigger to notification in 4 stages
Alert rule evaluates true against current metrics
First matching rule determines severity and target
Escalation chain begins with first-round targets
Phone, SMS, push notifications dispatched