2 out of 5.0, Reviewed Mar 3, 2016
HP's APM solution was complex to implement, build, maintain/upgrade, and on-board. Solution has scalability issues with no perceivable cost effective methods for growth. Vendor training was limited and difficult to acquire.
Don't believe the sales hype. Prove the capabilities on-premise, with complex applications, in your IT ecosystem.
BPM/synthetics are best of breed and served us well for many years.
Technical complexity. Too many distint technologies required to achive the vision.
Don't outsource pre-sales engineering. We always have to look to their "preferred providers" for pre-sales design. I don't believe they are as knowledgeable, or accountable, as dedicated HP employees would be.
Assess competitors (quadrant leaders). Start SaaS and work back to on-prem only as needed. Extend production focus to include broader app lifecycle, dev (DevOps)
3 out of 5.0, Reviewed Dec 7, 2015
There were a number of technical issues related to the tool crashing during capture of the scenario and during playback. After enough escalations between HP and the outsourcer, they brought enough technical resources to bear to resolve the showstoppers. However, the solution is brittle, in the sense that, once you begin customizing the code, you can no longer use the GUI tool to edit the scripts.
Take the pain up front of careful design, bitmap-based synchronization and hand coding-or you may ultimately find your results to be meaningless.
The overall design of the product components and architecture is very solid, including ways to function through firewalls. It manages system components well, and HP seems to have a good approach with the cloud model and pay-per-user-minute licensing.
The lack of flexibility in maintaining code via GUI elements once the scripts were modified.
It would be ideal if the GUI were fore more tuned to iteratively modifying and improving scripts, instead of being biased toward throwing away and re-capturing a scenario.
Very carefully craft the scenario scripting with many synchronization steps to along the way. This requires careful thought and is time consuming but pays dividends as one scales up the load of the environment.
Many features and capabilities.
HP LoadRunner support (EMEIA) and was very responsive and quickly brought development resources into the cases when it was clear there was a software defect. Hotfixes were produced quickly.