The "direct connection" you refer to that is used by LoadRunner and other products like it is actually a presentation of a subset of the available performance monitoring data that arises from the resources of the server stack. Which, ifyou know your technology, is typically quite remarkable.
We looked at that a long time ago and decided that we would NEVER have the resources to reproduce such sophisticated server-side monitoring, and that to have a selected subset of that information delivered to an eValid-based screen seemed, well, somehow like cheating the user. "Here, this is the performance data you need," we would be saying, with full knowledge that it is a subset of what is otherwise directly available. Any convenience to the user that would support would be outweighed by the message we would be [implicitly] sending, that other data from the server would NOT be of interest. When we know it could be.
Instead, we STRONGLY recommend using the server-side performance monitoring instrumentation, and rely on eValid to produce the realistic loading that makes that server side data meaningful and useful.
eValid Architecture Team