[{"data":1,"prerenderedAt":79},["ShallowReactive",2],{"term-p\u002Fpostmortem":3,"related-p\u002Fpostmortem":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":16,"meta":44,"navigation":45,"path":46,"related":47,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fp\u002Fpostmortem.md","Postmortem",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A Postmortem is the meeting you have after an incident to figure out what went wrong and how to prevent it from happening again. In a blameless postmortem, you focus on the system and process failures, not the people. The output is a list of action items to improve things.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A postmortem (also called post-incident review) is a structured analysis conducted after an incident to identify root causes, contributing factors, and remediation actions. Blameless postmortems (popularized by Google SRE) focus on systemic issues rather than individual blame to encourage honest reporting.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Write the postmortem document by end of day Friday.\" \u002F \"The postmortem showed three systemic issues that led to the outage.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"cicd","A Postmortem is the meeting you have after an incident to figure out what went wrong and how to prevent it from happening again.","intermediate","md",{},true,"\u002Fterms\u002Fp\u002Fpostmortem",[48,49,50,51,52],"Incident","Incident Response","SRE","Runbook","Chaos Engineering",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fp\u002Fpostmortem","KTTPExZ-wESD1ARBX08ALwPekLiwYElAbXD0d4l-Y-4",[60,65,69,72,75],{"title":52,"path":61,"acronym":6,"category":62,"difficulty":63,"description":64},"\u002Fterms\u002Fc\u002Fchaos-engineering","testing","advanced","Imagine stress-testing a bridge by parking trucks on it before opening day instead of hoping it holds.",{"title":48,"path":66,"acronym":6,"category":40,"difficulty":67,"description":68},"\u002Fterms\u002Fi\u002Fincident","beginner","An incident is when something has gone wrong in production and users are affected.",{"title":49,"path":70,"acronym":6,"category":40,"difficulty":42,"description":71},"\u002Fterms\u002Fi\u002Fincident-response","Incident Response is the process your team follows when production breaks. Who gets paged? Who's the incident commander?",{"title":51,"path":73,"acronym":6,"category":40,"difficulty":42,"description":74},"\u002Fterms\u002Fr\u002Frunbook","A Runbook is a step-by-step guide for handling a specific operational task or incident.",{"title":50,"path":76,"acronym":77,"category":40,"difficulty":42,"description":78},"\u002Fterms\u002Fs\u002Fsre","Site Reliability Engineering","SRE is Google's version of DevOps with a more engineering-focused twist.",1776518302818]