1. The Case of the SQL Stored Procedure Slowdown Explore Featured Editorials (Feb 21 2012) The combination of Prelert's advanced analytics and correlation capabilities with CA Introscope rich monitoring capabilities let users cut the time to finding the root cause of issues by 90%.  In a recent example, an Introscope administrator was trying to resolve an issue, in an unfamiliar application, resulting in a slowdown in a SQL stored procedure (> 200 seconds). The Introscope system was monitoring over 2700 unique metrics.  Prelert had narrowed this down to 24 metrics, which were directly related to the issue. Prelert's Activity View is a scrolling time window that allows the user to scroll back in time ... (Read Full Article)

   Comment Mentions:   Prelert   Root Cause   Analytics

2. No More 90 Minute Troubleshooting Calls for Credit Company Explore Featured Editorials (Jan 18 2012) Prelert Blog 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 ... (Read Full Article)

   Comment Mentions:   Prelert   Troubleshooting

1-2 of 2