COMMENTS
William, BPM and UtilityStatus.com provide deep dive as well as accumulated cpu elpased time across SOA applications and Business Processes the tool you are referring to is a developer tool. SLA management and cost management seems to be very challenging. With UtilityStatus the breakdown in usage is tied to a user transaction or service for example. This simplifies management as well enables multi-tenant architecture support. If you accumulate everything on the box for a customer you cannot share compute resources in a cloud.
The tool is not a developer tool it is production oriented out-performing all other competitors in benchmarks (SPECjvm2008) by ourselves and customers. A challenge we presented to each vendor at the recent JavaOne conference. None accepted.
Admittedly it offers the same runtime, model and process, visualization console across the complete application life cycle - but for most that is an advantage.
It is activity based but an activity which is mapped to an composite/hierarchal named group can represent any execution abstraction including a business transaction, resource transaction, request, operation, event, method. Tagging also supports alternative costing structures including organization, departments, units, users, txid.....
The screenshots show named groups mapped to class names but the software runtime itself is completely unaware of what a class or method is hence our support for metering of multiple meta and scripting languages in the same runtime.
William
Addtionally UtilityStatus provides tools for developers to provide Heap Dump Analysis and Thread Analysis across the cloud. This has shown to help manage applications across hundreds of application servers. Most customers have even replaced OEM since this Tool provides monitoring and management end-to-end include database performance based on actual requests.
Also interesting with UtilityStatus is the In-flight request analysis for example with long hanging threads in the risk analysis financial space you can see why a thread is hanging all the way down to the method level, real-time and in-flight.