Alerting rules reference
Last updated Jun 28, 2026
On this page
Alert rules decide when a failing check becomes a paged human.
Conditions
- Failure threshold — consecutive failed checks before an incident opens (default 2; set 1 for critical paths, 3+ for flaky third parties)
- Region quorum — require failures from N of 3 regions to filter out regional network noise (default 2)
- Response assertions — status code ranges, body substring/JSON path matches, and max latency
Routing
Rules map monitors → escalation policies. The most specific match wins: monitor-level rule → tag-level rule → workspace default.
Quiet hours & maintenance
Scheduled maintenance windows suppress paging but still record check results, so your uptime history stays honest.