Skip to main content

How to reduce time spent on high severity incidents

During most high severity incidents, a large portion of time is spent on measuring the scope and severity of a problem, followed by identifying the root cause. Actually writing a fix is often the smallest amount of time spent on MTTR (Mean Time To Recovery). This session covers key concepts that are often overlooked within the application observability space that will allow you to reduce the amount of time spent on reacting to incidents and increase the amount of time you can spend on what really matters.