The new version gets traction tracing and exception flagging, which at first blush don’t sound all that exciting, as those capabilities are readily available in most transaction monitoring tools. But the difference, claimed Chris Farrell, vice president of marketing and product management, is that because ClearApp uses a model-based approach, some goodies are added to both features that place transaction problems in much better context.
For instance, with the model, you can take the path of a failed or bottlenecked transaction and run an analysis to see what other transactions took that same path. By doing that, you can see if the error was a fluke or the sign of a more prevalent problem. In turn, you can drill down on those problematical transactions falling into the pattern and trace the exact paths to smoke out the problem.
The same capability extends to hung transactions that often fall between the cracks with traditional, agent based tracking tools. In those cases, agents can’t always measure something that hasn’t been completed, claimed Farrell. And in turn, you can perform similar pattern matching drilldowns when alerts pop up, such as that performance of too many transactions are falling beneath a certain threshold.
Other features of the latest release of QuickVision, version 7, include tracking of Web Service Remote Portlet (WSRP) relationships, which comes in useful for portlets in services-oriented environments that might be highly federated. (WSRP is an Oasis standard for exposing portlets as web services.) Also, a new feature tracks growth of memory leaks, plus several; enhancements to the user interface.
