Beyond the Mean Time To Repair


Mean time to Repair (MTTR) has long been the defacto metric for those tapped with the responsibility of up-time. It’s the cornerstone measurement of how well teams respond to service disruptions and a key performance metric that nearly all in IT should aim to consistently improve. Swift recovery provides far more benefits than attempts to engineer failure from complex systems.

As important as MTTR has become, the mean time to repair is no more than an average of how long it took to manage individual incidents (from acknowledgement to resolve) over the course of time. The number of data points during that time can vary greatly depending on the complexity and scale of systems. Furthermore, averages assume there is a normal event or that your data is a normal distribution. Anyone who has been on-call can attest that some incidents require longer to resolve than others and that variance is something you shouldn’t ignore.

Within any time-series dataset there are in fact high and low values hidden within the data. These outliers may indicate that while we think the time it takes to recover from failure is good, bad, or otherwise, many high values in our average distort or hide lower values and vice versa. We may believe that our efforts to reduce the time it takes to recover from failure is in fact working when the truth is it’s not.

In this talk, we’ll discuss the metric of Mean Time To Repair as well as additional methods of understanding data related to building and maintaining reliable systems at scale. MTTR must be made a priority for any IT team that habitually follows old-view approaches to incident response however; a deeper understanding of the data provides much higher fidelity regarding the true health of your systems and the teams that support them.

Audience takeaways:

  • Clear understanding of MTTR and why it has become a significant metric for modern DevOps/Operations teams
  • The Law of Averages
  • Additional metrics to provide deeper understanding of incident response
    • Mean Time to Identify
    • Median
    • Standard Deviation
    • Percentiles

Graphic Recording Beyond the Mean Time To Repair

Speaker

jason-hand

Jason Hand

 

DevOps Evangelist at VictorOps, organizer of DevOpsDays - Rockies, author of “ChatOps for Dummies”, co-host of “Community Pulse” (a podcast on building Community within Tech), and host of a number of DevOps related events in the Denver/Boulder area. Jason has spent the last 20 months presenting and building content on a number of DevOps topics such as Blameless Post-mortems, ChatOps, and the value of context within incident management. A frequent speaker at DevOps events around the country, Jason enjoys talking to audiences large and small on a variety of technical and non-technical subjects.