[{"data":1,"prerenderedAt":151},["ShallowReactive",2],{"term-r\u002Frunbook":3,"related-r\u002Frunbook":133},{"id":4,"title":5,"acronym":6,"body":7,"category":114,"description":115,"difficulty":116,"extension":117,"letter":118,"meta":119,"navigation":71,"path":120,"related":121,"seo":127,"sitemap":128,"stem":131,"subcategory":6,"__hash__":132},"terms\u002Fterms\u002Fr\u002Frunbook.md","Runbook",null,{"type":8,"value":9,"toc":108},"minimark",[10,15,19,23,26,30,97,101,104],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A Runbook is a step-by-step guide for handling a specific operational task or incident. It's like the instruction manual for when things go wrong — 'database is slow, follow these steps.' When you get paged at 3am with a foggy brain, a good runbook means you don't have to figure everything out from scratch.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A runbook is a documented set of procedures for performing operational tasks, particularly for incident response. They range from fully automated (auto-remediation scripts) to human-executed checklists. Runbooks reduce MTTR, enable junior engineers to handle incidents, and capture institutional knowledge.",[11,27,29],{"id":28},"show-me-the-code","Show Me The Code",[31,32,37],"pre",{"className":33,"code":34,"language":35,"meta":36,"style":36},"language-markdown shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","# Runbook: Database Connection Exhausted\n## Symptoms\n- 503 errors on \u002Fapi endpoints\n- DB connection pool metric > 95%\n\n## Steps\n1. Check active connections: SELECT count(*) FROM pg_stat_activity\n2. Kill idle connections: SELECT pg_terminate_backend(pid)...\n3. Restart app pods: kubectl rollout restart deployment\u002Fapi\n","markdown","",[38,39,40,48,54,60,66,73,79,85,91],"code",{"__ignoreMap":36},[41,42,45],"span",{"class":43,"line":44},"line",1,[41,46,47],{},"# Runbook: Database Connection Exhausted\n",[41,49,51],{"class":43,"line":50},2,[41,52,53],{},"## Symptoms\n",[41,55,57],{"class":43,"line":56},3,[41,58,59],{},"- 503 errors on \u002Fapi endpoints\n",[41,61,63],{"class":43,"line":62},4,[41,64,65],{},"- DB connection pool metric > 95%\n",[41,67,69],{"class":43,"line":68},5,[41,70,72],{"emptyLinePlaceholder":71},true,"\n",[41,74,76],{"class":43,"line":75},6,[41,77,78],{},"## Steps\n",[41,80,82],{"class":43,"line":81},7,[41,83,84],{},"1. Check active connections: SELECT count(*) FROM pg_stat_activity\n",[41,86,88],{"class":43,"line":87},8,[41,89,90],{},"2. Kill idle connections: SELECT pg_terminate_backend(pid)...\n",[41,92,94],{"class":43,"line":93},9,[41,95,96],{},"3. Restart app pods: kubectl rollout restart deployment\u002Fapi\n",[11,98,100],{"id":99},"when-youll-hear-this","When You'll Hear This",[16,102,103],{},"\"Write a runbook for the most common incidents so the on-call rotation isn't miserable.\" \u002F \"Follow the database runbook — don't improvise during an incident.\"",[105,106,107],"style",{},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":36,"searchDepth":50,"depth":50,"links":109},[110,111,112,113],{"id":13,"depth":50,"text":14},{"id":21,"depth":50,"text":22},{"id":28,"depth":50,"text":29},{"id":99,"depth":50,"text":100},"cicd","A Runbook is a step-by-step guide for handling a specific operational task or incident.","intermediate","md","r",{},"\u002Fterms\u002Fr\u002Frunbook",[122,123,124,125,126],"Playbook","Incident Response","On-call","Postmortem","SRE",{"title":5,"description":115},{"changefreq":129,"priority":130},"weekly",0.7,"terms\u002Fr\u002Frunbook","oG1B1p05QxPNRG5Ntxnklcn7ZzKuYym8Cy0INvZjwbE",[134,137,141,144,147],{"title":123,"path":135,"acronym":6,"category":114,"difficulty":116,"description":136},"\u002Fterms\u002Fi\u002Fincident-response","Incident Response is the process your team follows when production breaks. Who gets paged? Who's the incident commander?",{"title":124,"path":138,"acronym":6,"category":114,"difficulty":139,"description":140},"\u002Fterms\u002Fo\u002Fon-call","beginner","On-call means it's your turn to be the person who gets woken up at 3am if production breaks.",{"title":122,"path":142,"acronym":6,"category":114,"difficulty":116,"description":143},"\u002Fterms\u002Fp\u002Fplaybook","A Playbook is like a runbook but bigger — it covers a whole category of operations, not just one specific scenario.",{"title":125,"path":145,"acronym":6,"category":114,"difficulty":116,"description":146},"\u002Fterms\u002Fp\u002Fpostmortem","A Postmortem is the meeting you have after an incident to figure out what went wrong and how to prevent it from happening again.",{"title":126,"path":148,"acronym":149,"category":114,"difficulty":116,"description":150},"\u002Fterms\u002Fs\u002Fsre","Site Reliability Engineering","SRE is Google's version of DevOps with a more engineering-focused twist.",1776518309222]