on-call
Being the person responsible, for a set period, for responding when a production system raises an alert, often outside working hours.
In more detail
A page is the notification that reaches the on-call person. Useful alerts, clear runbooks and readable failure messages shorten the time from page to diagnosis. Test that notifications reach whoever is currently on call.
Examples
The course alarm plan pages payments-on-call when p99 latency stays above two hundred milliseconds.Time-based escalation pages the on-call person when a case is not acknowledged in time, and pages the next level if they do not answer.In this course: The on-call engineer at three in the morning is the real audience for test names and failure reports: they need to understand what broke without opening the code. Clear names and reports shorten the time from alert to diagnosis.Related terms
- alarm — A rule that watches a metric and changes state, and notifies someone, when the metric crosses a threshold for long enough.
- runbook — A written, step-by-step procedure for a routine operation or for responding to a known kind of incident.
- incident — An unplanned event that degrades or interrupts a service for its users, or harms the security of systems or data.
- alert — An automatic notification sent when a monitored condition, such as a high error rate, stays true.
- escalation — Bringing in more people, expertise or authority when a problem exceeds the current responder.
- on-call page — An urgent alert that interrupts the on-call engineer, for example on their phone, because a person must act now.
- escalation path — The agreed route a case takes when it needs more skill, more authority or has waited too long.
- production — The live environment where real users use the service, as opposed to development or testing.
- failure report — What the test runner prints when a test fails: which test, which line, and the values that did not match.
- test naming — Choosing test function names that state the behaviour and the condition, so a failure summary reads as a sentence.
Taught in
- Two Hundred Accounts And One Bad Deploy — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Strategies Across Compute: The Canary That Saw Nothing — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- High Availability Across Tiers: What Fails Over By Itself? — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Testing Resilience: The Experiment That Would Have Been The Outage — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Collecting Logs And Metrics: The Disk Nobody Measured — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Finding The Problem: The Composite Alarm That Stayed Quiet — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Monitoring As Code: The Alarm That Watched Nothing — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Incident Tooling: Eighteen Minutes To Find A Human — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Regions, Availability Zones and Reliability — Cloud Infrastructure & Hyperscaler Architecture
- Metrics, Logs, and Alarms — Cloud Infrastructure & Hyperscaler Architecture
- What DevOps Actually Is — DevOps & Site Reliability Engineering
- Error Budgets — DevOps & Site Reliability Engineering
- On-Call And Incident Response — DevOps & Site Reliability Engineering
- The Incident Lifecycle — DevOps & Site Reliability Engineering
- Dashboards That Answer Questions — Full-Stack Observability: Metrics, Tracing & Logging
- Alerting On Symptoms Versus Causes — Full-Stack Observability: Metrics, Tracing & Logging
- On Call And Incident Command — Full-Stack Observability: Metrics, Tracing & Logging
- Ninety Nine Percent Of What? SLIs, SLOs And SLAs — Prometheus Certified Associate (PCA) Exam Prep
- The Server That Would Not Die: Selecting Data — Prometheus Certified Associate (PCA) Exam Prep
- Forty One Buzzes: Routing Alerts With Alertmanager — Prometheus Certified Associate (PCA) Exam Prep
- One Week, Three Objectives: Final Review — Prometheus Certified Associate (PCA) Exam Prep
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture
- The Cost And Value Of A Test — Automated Testing, TDD & Quality Engineering
- Arrange, Act, Assert — Automated Testing, TDD & Quality Engineering
- Naming Tests For Readability — Automated Testing, TDD & Quality Engineering
References
- AWS Systems Manager Incident Manager: on-call schedules
- Google SRE book: Being On-Call
- Google SRE workbook: On-Call
- NIST SP 800-61 Rev. 3: Incident Response Recommendations