Why Most Incident Postmortems Miss the Mark and How to Fix Them

This article reveals three common pitfalls in daily incident postmortems—overlooking minor failures, confusing root causes with triggers, and weak improvement actions—and offers practical steps like the 5 Whys method and essential corrective measures to truly reduce online outages.

Continuous ImprovementRoot Cause AnalysisSRE

0 likes · 5 min read

Why Most Incident Postmortems Miss the Mark and How to Fix Them

Didi Tech

Nov 23, 2023 · Operations

Root Cause Analysis of Java Process Termination Caused by Linux OOM Killer Triggered by Vim Opening a 37 GB Log File

The Java service crashed when the Linux OOM killer terminated its process after a developer opened a 37 GB log file with Vim, which loaded the entire file into the container’s 8 GB memory, triggering a port alarm and prompting investigation and recommendations to use streaming tools instead of Vim.

ContainerJavaOOM killer

0 likes · 8 min read

Root Cause Analysis of Java Process Termination Caused by Linux OOM Killer Triggered by Vim Opening a 37 GB Log File

Xiaohe Frontend Team

Nov 10, 2022 · Operations

What Went Wrong with Our Multi‑User Live Audio Feature? A Post‑Mortem and Lessons Learned

This post‑mortem reviews a chaotic multi‑person live‑audio incident, detailing its background, symptoms, timeline, root causes, and the improvement plan, offering practical insights for better release planning, gray‑release strategies, and risk awareness in software operations.

Hot UpdateSoftware Operationsgray release

0 likes · 7 min read

What Went Wrong with Our Multi‑User Live Audio Feature? A Post‑Mortem and Lessons Learned

Why Most Incident Postmortems Miss the Mark and How to Fix Them

Root Cause Analysis of Java Process Termination Caused by Linux OOM Killer Triggered by Vim Opening a 37 GB Log File

What Went Wrong with Our Multi‑User Live Audio Feature? A Post‑Mortem and Lessons Learned

Root Cause Analysis of Java Process Termination Caused by Linux OOM Killer Triggered by Vim Opening a 37 GB Log File