From the course: DevOps Foundations: Effective Postmortems
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Why postmortems?
From the course: DevOps Foundations: Effective Postmortems
Why postmortems?
- [Instructor] Most of you have heard of a postmortem, or maybe an autopsy or accident investigation, or maybe by a less gruesome name, like a retrospective, after-action review, or even lessons learned or learning review. I actually prefer to say incident retrospective myself, because hopefully, your systems aren't actually dead for good. Otherwise, you'd be out of a job. But postmortem is the most commonly accepted term, so we'll use it in this course. So, you also probably have heard the general idea of what a postmortem is and why you would do one for technical incidents. You look back on an unusual, catastrophic computer problem you had, identify its root cause, and either discipline the person at fault or fix something so it won't happen again, right? Here's the problem. Everything about that definition is wrong. Conducting incident postmortems requires clear and precise thinking, so let's start now. First of…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.