This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own

View analytic
Tuesday, August 4 • 14:00 - 15:15
Incident Response Patterns: What we have learned at PagerDuty (Arup Chakrabarti)

Sign up or log in to save this to your schedule and see who's attending!

Limited Capacity seats available

At PagerDuty, we see how engineers across the industry are resolving incidents. Some teams take days to resolve problems, some take minutes, and most are somewhere in between.
In this talk, we will cover some learnings that we have had internally at PagerDuty from our own incidents, steps we have taken to get better at them, and how we run post-mortems. From there, we will also cover some trends across the industry: how long outages take, how many people have to get involved, how many teams actually fix their root causes, and how much sleep the average on-call engineer gets.

Learning Outcomes:
  • Best practices on incident response

avatar for Arup Chakrabarti

Arup Chakrabarti

Engineering Manager - Operations Engineering, PagerDuty
Arup has been working in the space of software operations since 2007. He started out at as an Operations Engineer at Amazon, helping to reduce customer defects with multiple teams for the Amazon Marketplace. Since then, he has managed and built operations teams at Amazon and Netflix to help improve availability and reliability. He currently works at PagerDuty, where he is part of the Operations Engineering Team.

Tuesday August 4, 2015 14:00 - 15:15
Potomac 5/6