Why Modern Application Monitoring Needs 15 Second Granularity
You have certainly heard by now about the importance of high performing applications and how less-than-perfect end user experience can impact your brand, revenue, user satisfaction and user retention. What does that mean in practical terms? How fast is fast? How slow is slow?
Well, most industry experts agree that slow begins around three seconds. When an end user launches a mobile app or they bring up your website and the response time exceeds 3 seconds, you begin seeing users drop. In fact, studies show that 40% of people abandon a website that takes more than 3 seconds to load.
This means that identifying an underperforming business transaction impacting your customers must be done in a timely, efficient manner. Some application monitoring tools report response times at a 1 minute refresh rate. “How much more real-time do you need?”, they claim. Let’s explore that for a moment.
Assuming you’re reading this on a desktop browser, grab your smart phone for a quick experiment. Start the Stopwatch. Then open an app like your mobile banking app. Login. Check your balance. Logout. Then check the time.
I can perform those four business transactions of Login, Select Account, View Balance, and Logout in about 25 seconds start to finish. (This is not an ad for my bank, by the way, so I’ll leave the name out!) Anyway, that means each step, each business transaction, for me took about 2-3 seconds with a few seconds in between each for my navigation. What was your experience?
Now consider this (maybe even start the stopwatch to let it continue to 1 minute). You’d be surprised how long those next 35 seconds seem to take!
Now imagine you’re monitoring those business transactions and the first step of Login and authentication is slow – maybe it even fails or times out. What if it is happening across thousands of customers? How quickly would you want to be notified?
Why you need 15 second granularity
CA Application Performance Management (APM) monitors all transactions, all the time, reporting within 15 seconds! This means, within the first few seconds of slowness or failure, your team could be notified of users experiencing problems trying to login.
If you think about it, what do most users do if they fail on login? They try again, of course! Or what if it’s slow? After several seconds, they may restart the app or hit refresh on the browser; a cycle that can occur over and over…resulting in additional login transactions submitted, adding to the “log jam” of performance issues.
Now what if you’re monitoring at 1-minute intervals like many application monitoring tools do? Well, that means I could have tried and experienced a slow or failed login multiple times within a 1 minute window before the tool reports the first occurrence. It’s likely I’m not the only user logging in at this point in time which means how many others users might be impacted as well within that 1 minute time range before Operations even has the first indication an issue exists?
With CA Application Performance Management, latency and errors are detected immediately so operations and application teams are notified at the first 15 second interval – four times sooner than with 1 minute reporting tools. How quickly would you want to know about a performance issue plaguing your end users? The point rings even truer if we move from the banking example to one where revenue could be immediately affected by an app teams’ slow response to poor performance – say a retail site on Black Friday or a Flower Delivery service right before Mother’s Day or an electronics site right before the new smartphone launch. I think you get the idea.
In today’s App Economy, users expect high performing, high quality, fast responding apps. App teams should expect no less from their application monitoring tool…
Still not convinced? Check out this video to see how 15 second granularity can make a difference.