create-operational-runbook

To create an operational runbook, provide your incident context and system scenario to generate a complete document with headers, investigation procedures, resolution steps, and post-resolution actions tailored for on-call engineers.

An SRE runbook should include explicit prerequisites, investigation procedures, resolution commands, verification steps, rollback paths, success criteria, and cross-references to design docs to ensure safe and auditable incident responses.

The best way to document rollback procedures is to structure them within a comprehensive runbook that explicitly defines resolution actions, verification commands, and success criteria to eliminate ambiguity during outages.

Yes, you can generate a runbook that cross-references your system architecture and dependencies, ensuring the incident response procedures reflect the current design and operational constraints of your infrastructure.

To maintain runbooks after an incident, follow the generated post-resolution steps and maintenance sections to update procedures, ensuring documentation stays aligned with current system architecture and operational requirements.