Incident Ready: How to Chaos Engineer Your Incident Response Process
We’re pretty sure using a real incident to test a new response process is not the best idea. So, how do you test your process ahead of time? Learn how to use chaos engineering principles to stress test your incident management process.
By The FireHydrant Team on 10/15/2020
Don’t let a T-Rex ruin your process
We’re pretty sure using a real incident to test a new response process is not the best idea. So, how do you test your process ahead of time?
In this video, FireHydrant CEO, Robert Ross, shared how our customers leverage best practices to break, mitigate, resolve, and fireproof incident processes. He shares a great reminder that:
In case you couldn’t see the image, it’s a giant image that says “People mitigate incidents, not processes.”
To help you avoid a process breakdown, Robert will walk you through how to leverage chaos engineering philosophies to stress test 3 critical parts:
When and how you declare an incident
How you communicate an incident - internally and externally
When and if you should escalate an incident to your stakeholders
Watch the video below
Interested in more content like this? Subscribe to our emails for updates, events, and giveaways.
See FireHydrant in action
See how service catalog, incident management, and incident communications come together in a live demo.Get a demo