Showing Post-Incident Review Posts

Finally, the last part of The DevOps Dictionary is here! We covered letters A-O in parts one and two. Today, we’ll finish the series of...

We’re back with more of The DevOps Dictionary, a list of the most important terms and DevOps definitions. Part One covered letters A-I, and part...

We decided to embark on a journey to make our systems more reliable by creating intentional chaos. Our team developed the SRE Council, made up...

Resolving incidents quickly and mitigating downtime is essential when disaster strikes. However, the importance of the post-incident review after an incident occurs can’t be overstated....

Many sources maintain the goal of incident management is simple: to restore service as quickly as possible. When an issue occurs and a system breaks,...

Systems fail, servers go down, shit breaks. With the pressure of continuous uptime and world-class customer experience, we’re being asked to build, deploy, and operate...

The Analysis phase of the Incident Lifecycle occurs after an incident is resolved, and focuses on learning. This phase is often referred to as a...

Over the course of the last three blog posts on my eBook, Post-Incident Reviews, Learning from Failure for Improved Incident Response, I’ve shared recommended methods...

As we dive further into the eBook, Post-Incident Reviews, Learning from Failure for Improved Incident Response, we’ll explore how using analysis as an avenue for...

When incidents occur, the natural response is to investigate and pinpoint the cause before looking for a solution. However, this traditional approach assumes that causality...