A runbook is an operational document that helps on-call engineers diagnose recurring production problems, apply known fixes, and escalate issues when necessary. section 16.1
A useful runbook records:
- Procedures for common failures and recurring load patterns. section 16.1
- The people or vendors to contact when the on-call team cannot resolve an incident. section 16.1
- The tools needed for investigation, including logs, metrics, alerts, dashboards, configuration, and source documentation. section 16.1
Handling a usage spike
When a large customer creates a sudden load increase, the runbook can provide a recipe for starting additional system instances and scaling them down after demand returns to normal. section 16.1
