Glossary term
What is Runbook? Meaning for developers
In System Design
Step-by-step instructions for handling an alert. Example: "If checkout errors spike: check deploys, then…".
Learn it properly · System DesignLesson 48: Monitoring, Alerting & Blameless PostmortemsSixty alerts a week, fifty-five that don't matter — so the real one gets snoozed and customers can't pay for two hours. How to build dashboards and alerts people trust, run incidents with clear roles, and write blameless postmortems that actually make the system better.In Scenario Debugging
Step-by-step instructions for a known alert or failure. The alert itself links to it.
Learn it properly · Scenario DebuggingLesson 10: Production Incidents: Step-by-Step GuideDetect, reduce the harm, find the cause, tell people, fix, learn. Roll back first, roles and severity, and eleven incident cases from latency that doubled overnight to a vulnerability found in production.In Team Lead Mindset
A short document with the steps to handle a known problem or alert.
Learn it properly · Team Lead MindsetLesson 16: Scaling Teams, Ownership and On-CallSplitting teams with Conway in mind, a service catalogue, humane on-call, avoiding hero culture, toil and cross-team dependencies.In Observability & SRE
A short written guide that says what to check and try when a given alert fires.
Learn it properly · Observability & SRELesson 5: Alerting and Dashboards That People TrustAlerting on symptoms, avoiding alert fatigue, runbooks, dashboard design, and burn-rate alerts with a worked example.