symptom-based alerting
Paging on what users feel, such as errors, slowness or unavailability, rather than on internal causes such as high CPU or a restarted process.
In more detail
A cause can change without harming users, and one symptom can have many causes, so cause alerts produce noisy urgency. Keep causes on dashboards and in runbooks as investigation evidence, and page when the customer-facing symptom is urgent.
Related terms
- alert — An automatic notification sent when a monitored condition, such as a high error rate, stays true.
- alert fatigue — The state where people receive so many unhelpful alerts that they start ignoring them, including the real ones.
- service level objective — A target for a service level indicator over a time window, such as 99.9 per cent of checkouts succeeding over 30 days.
- runbook — A written, step-by-step procedure for a routine operation or for responding to a known kind of incident.
Taught in
- Observability Versus Monitoring — Full-Stack Observability: Metrics, Tracing & Logging
- Dashboards That Answer Questions — Full-Stack Observability: Metrics, Tracing & Logging
- Traces, Spans And Context Propagation — Full-Stack Observability: Metrics, Tracing & Logging
- Bringing The Three Signals Together — Full-Stack Observability: Metrics, Tracing & Logging
- Alerting On Symptoms Versus Causes — Full-Stack Observability: Metrics, Tracing & Logging
- Alerting Rules And The For Duration — Full-Stack Observability: Metrics, Tracing & Logging
- Service Level Indicators — Full-Stack Observability: Metrics, Tracing & Logging
- Service Level Objectives — Full-Stack Observability: Metrics, Tracing & Logging
- Error Budgets And Burn Rate Alerts — Full-Stack Observability: Metrics, Tracing & Logging
- A Worked Example Postmortem — Full-Stack Observability: Metrics, Tracing & Logging