Hi!
> It's interesting for benchmarking and stress testing a bean. But you'd
also
> need to build micro benchmark tests that fed the bean with as many calls
> per second as possible to be able to compare the results.
>
> This is of course useful as well but not quite what I was after. I'm more
> interested in being able to plug in a monitor to a "live" system, to be
> able to easily visualize which parts of the system take up the most
> execution time, which users/groups are accessing them and how often, and
> break it down to application/bean or even method level. This should allow
> the admin/developer to identify the parts of the system that should be
> considered for increased optimization and find potential bottlenecks. I
> think it's valuable to be able to monitor a deployed application in its
> normal usage scenario. This is something you will want to do if you plan
on
> hosting services, for example.
>
> Anyhow, there are probably more than one part of the architecture that can
> publish interesting results to the same metrics topic. Invocation layer
was
> just the most obvious one so I decided to give it a shot first.
You are quite correct. Agree.
/Rickard
