DevOps Articles

A Crash Course on Incident Response, Part 2

In Part 1, I discussed the important aspects of a good incident management practice including effective communication, clearly defined stakeholders, and getting timely resolution. Before you can give quality updates during an incident, you need to have good information to share. This section will dive into some practical aspects of getting good information and managing an incident to resolution.

The incident commander is responsible for ensuring communications happen, but that doesn’t mean they have to author all of them.

In the midst of an incident is the worst possible time to take shortcuts and bypass safeguards such as code reviews.