DEV Community

Patchy from FireHydrant for FireHydrant

Posted on

Pragmatic Incident Response: 3 Lessons Learned from Failures

In my past experience as an SRE I’ve learned some valuable lessons about how to respond and learn from incidents.

  1. Declare and run retros for the small incidents. It's less stressful, and action items become much more actionable.

  2. Decrease the time it takes to analyze an incident. You'll remember more, and will learn more from the incident.

  3. Alert on pain felt by people — not computers. The only reason we declare incidents at all is because of the people on the other side of them.

Let’s dive into each of these lessons a little deeper, and how they can help you build a better system for pragmatic incident response.

Read the full post here.

This post was originally published on the FireHydrant Blog on July 15, 2021 by Robert Ross.

Heroku

Built for developers, by developers.

Whether you're building a simple prototype or a business-critical product, Heroku's fully-managed platform gives you the simplest path to delivering apps quickly — using the tools and languages you already love!

Learn More

Top comments (0)

AWS Q Developer image

Your AI Code Assistant

Automate your code reviews. Catch bugs before your coworkers. Fix security issues in your code. Built to handle large projects, Amazon Q Developer works alongside you from idea to production code.

Get started free in your IDE

👋 Kindness is contagious

If this post resonated with you, feel free to hit ❤️ or leave a quick comment to share your thoughts!

Okay