No More 90 Minute Troubleshooting Calls for Credit Company

Featured Editorials (Jan 18 2012) Prelert Blog

1. 

   Introscope admins at a major credit bureau were frustrated over the typical 90 minutes they spent on conference calls just trying to figure out where to start the troubleshooting process.  They gave Prelert a chance by feeding it data from a recent incident where CPU utilization for the Websphere JVM process pegged at 100% for 30 minutes resulting in the restart of multiple services for a critical production app.

   Prelert’s intuitive dashboard (shown below) allowed the admins to go back in time to view anomalous activities related to the CPU utilization spike.  Prelert identified a web service that took over 6 seconds to execute some 45 minutes before the problem. It also found an increase in the number of ‘errors’ reported from the end-user perspective just seconds prior to the increase in CPU utilization and correlated these errors to specific SQL calls.

   The Introscope administrators were impressed by Prelert’s ability to shorten a 90 minute call to 5 minutes, the ability to correlate specific SQL calls and identify a potential leading indicator to the problem.

    

    

    

   

    

   Bookmark or Share this article