As a follow up to the recent "Script Recycling for Fun and Profit webinar (link)" guest blogger HP APM Global Practice Lead Miron Mizrahi goes a bit further into the mechanics of Reusing test scripts to monitor application performance in production.....
Seagate's Steve Katz, a self-confessed "Scriptaholic" and longtime APM/BAC user, shares his battle-tested VuGen scripting tips and tricks to get the most from HP Application Performance Management....
- Are you attending our HP Software Universe event in Washington this year?
- Are you a current HP Business Service Management (BSM) customer - customer who has one or more products from
HP Business Availability Center (any of these products Business Process Monitor/Real user monitor/Sitescope/Diagnostics/Service Level Management/Transaction Vision)
HP Operations Management Center (Operations Manager, Operations Manager i, any of our SPIs)
HP Network Management Center (NNMi, Performance SPIs, etc)
- Are you happy with your BSM deployment and want to talk about it?
- Do you want to be seen as a leader and innovative company by having your BSM story quoted in press articles?
If you answered yes, to all of the above, then send an email to: aru@hp.com with your contact information (your name, company, email and phone number). I’ll call you and we can discuss how to give you and your BSM deployment some great exposure.
Thanks
Aruna Ravichandran
Group Product Marketing Manager
Application Performance Management ( part of BAC)
aru@hp.com
An ICT services provider to enterprises across the Middle East, Smartworld meets and exceeds its customers’ expectations with efficient, high-quality services. HP Business Service Management makes this possible by bridging IT silos and consolidating network, system, and application events. Integration with HP Service Manager enables proactive alerts and ticket creation, accelerating mean time to repair.
In the end, Smartworld optimized IT operations efficiency, delivered superior service levels, and reduced TCO by between 30 and 60%. Now that’s smart.
To learn more about the benefits of BSM at Smartworld
By Mike Shaw, BSM Product Marketing
Last year, we did a series of in depth interviews with customers (28 of them, actually). As part of these interviews, we asked if people did proactive user experience monitoring - either using synthetic scripting technology to pretend to be a user, or using a probe on the network to look at the data going to the users' screens and monitoring the response time.
About half the respondents said they did. This ties in with a recent Aberdeen study that found 57% of companies didn't do user experience monitoring.
So, we asked on IT manager who didn't do user experience monitoring, why had he not invested in this technology. "Because we respond very quickly when the first customer rings in", was his response.
And since that day, I've been on a quest to get a magic number. How many minutes, on average,elapses between a business service giving a poor user experience and the first customer calling in. I have only three data points, but no definitive study. The average seems to be about 30 to 45 minutes.
To get another angle, whenever I present to a friendly audience, I'll ask them how often they have called a company when they have had problems with a user interface (e.g. on an ordering web site). Of the 160 people I've asked, just two had actually picked up the phone, and in both situations, it's been something critical like sorting out a mobile/cell phone bill.
I have another data point. A study by Corporate Executive Board in 2004 found that the average cost to a company of down-time is $1.3m per hour. That's $27,000 per minute.
So, we have 30 to 45 minutes (very rough estimate). We have $27,000 per minute. Being conservative (and very rough), we have a cost of 30 minutes X $27,000 or $81,000 per poor user experience problem.
Do you have any data on the average time between a poor user experience situation starting and the first customer calling in? If you do, could you please post a comment with the data - it amazes me that such data is not readily available "out there".