Runbook Generator

A runbook is a documented set of procedures for operating and troubleshooting a system or service. It provides step-by-step instructions for common tasks and incident scenarios, enabling on-call engineers to respond quickly without relying on memory or tribal knowledge.

A good runbook includes: service overview, how the alert/incident is detected, immediate triage steps, investigation commands, escalation contacts, resolution steps, rollback procedure, and post-incident follow-up actions. The goal is that any on-call engineer — even unfamiliar with the service — can follow it.

These terms are often used interchangeably, but runbooks typically describe reactive procedures for specific operational tasks or alerts. Playbooks are broader operational guides covering multiple scenarios and decision trees. In practice, most teams call any operational procedure doc a runbook.

Runbooks should be updated after every incident as part of the post-incident review. Link runbooks from your alerting rules so on-call engineers find them instantly. Track runbook age — if a runbook hasn't been reviewed in 6 months, schedule a review. Consider runbook health as part of your reliability scorecard.

P0 (Critical): full outage or data loss — all hands, immediate response. P1 (High): major feature broken, significant revenue/customer impact — on-call engaged within 15 minutes. P2 (Medium): degraded performance or partial outage affecting some users — respond within 1-2 hours. P3 (Low): minor issue, workaround available — respond within 24-48 hours.