Modern QA2026Alert Design Principles — tiles
Log inJoin
40 / 67 · 06 Observability-Driven Testing · Metrics and Alerting← prev⊞ allnext →☰ Read as one page

6.6Alert Design Principles

  1. Alert on symptoms, not causes. Alert on "users are seeing errors" not "CPU is high." High CPU that causes no user impact is not an alert-worthy event.

  2. Use multi-window, multi-burn-rate alerts. Catch both sudden outages and gradual degradation.

  3. Every alert must have a runbook. If there is no documented response procedure, the alert is not ready for production.

  4. Page only for things that need immediate human action. Everything else should be a ticket, a dashboard, or a weekly report.

← Previous6.5 Multi-Burn-Rate Alerts