TAG | MTTR
I’ve got many years of performance geekery under my belt and I’ve learned many lessons during that time. One of the most important lessons is paying close attention to the distinction between data and information. Let’s take a look at how the dictionary defines each term:
Data – facts and statistics collected together for reference or analysis.
Information – facts provided or learned about something or someone.
What do these definitions reveal to us about data and information and how does it apply to monitoring tools? Let’s explore that together. I’ll provide specific examples along the way to illustrate my points.
The Problems with Data
Data is fundamental to problem solving, but I don’t want to have to dig through a bunch of data while my business critical, mission critical, revenue generating, etc… applications are down. To me, data is just like this picture…
We recently launched a new competition for our customers so they could share the success they’re having managing application performance with AppDynamics. It’s been just over a month since launch and already we’ve had some excellent submissions. Today I received another submission from Fox News on how they identified and resolved an application performance bottleneck in production using AppDynamics Pro. This is just one example of how Fox News was able to drastically reduce their mean-time-to-resolution, cut in half their number of severity 1 incidents, all of which resulted in cost savings of over $225,000 in their first year of deploying AppDynamics.
Below is their X-Ray which illustrates how AppDynamics was used to troubleshoot this production incident:
Appman.Link to this post:
I received an X-Ray from Covis Software GmbH in Germany who provides CRM solutions. They’ve been managing their .NET application performance with AppDynamics Pro for several months now in production. In the below X-Ray (as documented by the customer), Covis were able to improve the performance of a mission-critical business transaction from over 10 seconds to around 300 milliseconds, representing a 33x improvement. The business impact of such change meant average call time for some CRM agents dropped by almost 10 seconds.
App Man.Link to this post: