DevOps Foundations · Module 7: Operations, observability and backup · Lab
Rewrite a Broken Runbook So Someone Else Can Run It
50 min hands-on · Advanced
A deliberately broken runbook for a fixture incident (disk-full style); a partner or a time-boxed stranger run; all under /tmp/dlab-m07-03.
Two ways to do this lab: in your browser on Killercoda (free, no install), or on your own machine as a local guide. Killercoda runs one free scenario at a time: if you see a waiting queue, close other Killercoda tabs and wait a minute.
Objectives
- Rewrite the procedure to the stranger standard with stop conditions
- Hand it over silently and record every trip point
- Run the repaired procedure for real and log the change
Step 1
Rewrite to the standard
Rewrite with trigger, preconditions, exact commands plus expected outputs, decision points, done condition and stop conditions. Put it in version control.
Step 2
Hand over and watch
Give it to someone who has never run it, watch without helping, and record every hesitation, guess or improvisation as a document defect with its fix.
Step 3
Run it and log it
Run the repaired procedure against the fixture incident, verify the done condition, and write the change-log entry (who, what, when, why, reversal) as the incident would require.
How to confirm it worked
- Rewritten runbook carries all six elements including stop conditions
- Handover trip points recorded with a fix per point
- Clean supervised run completed with the done condition verified
- Change-log entry written in the required shape