escalation
Bringing in more people, expertise or authority when a problem exceeds the current responder.
In more detail
Runbooks and escalation policies should say when to escalate, such as after a set time or at once if data loss is suspected. Escalating before an incident outgrows one person's attention, permissions or expertise is cheaper than a long outage handled alone.
Related terms
- 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.
- on-call — Being the person responsible, for a set period, for responding when a production system raises an alert, often outside working hours.
- incident commander — The person who coordinates an incident response: assigning roles, making decisions and keeping the response moving, rather than debugging.
Taught in
- Metrics, Logs, and Alarms — Cloud Infrastructure & Hyperscaler Architecture
- Service Level Agreements: The Consequence Discriminator — 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
- Pipelines And GitOps Context — DevOps & Site Reliability Engineering