incident-runbook-templates

Structured incident response runbooks with detection, triage, mitigation, and communication procedures. Production-ready templates for incident response runbooks covering detection, triage, mitigation, resolution, and communication. Add a numbered checklist at the top of the runbook that mirrors the section numbers, so responders can track progress under stress without reading the full document: Runbooks rot because they're updated manually. Include a "Last Verified" date and owner at the top, and add a CI check that validates all curl endpoints and kubectl context names are still valid: Assign a dedicated incident communicator role (separate from the incident commander) whose only job is to post status updates. Add a standing agenda in the communication template: Add explicit warnings before destructive SQL commands and require a dry-run output check before executing: - Provides severity-level framework (SEV1–SEV4) with response time targets and impact classifications - Includes ready-to-use templates for service outages and database incidents with bash/SQL commands, health checks, and rollback procedures - Covers escalation matrices, communication templates for notifications and status updates, and verification steps to confirm resolution - Emphasizes runbook maintenance through regular testing, postmortem integration, and assumption documentation - Creating incident...