Marina Vatkina wrote:
> Monitoring team,
>
> I'm working on enabling ejb monitoring, which (besides call flow data)
> is tracked on per bean or bean method, and in v2 terms was the
> sub-tree of server.applications, added to is via a special registry.
>
> Q1. How do I do it in V3?
>
> Q1a. Which names would I use?
The names for what? Can you give an example?
>
> Q2. CallFlowInfo - this type was used in v2 to pass around the data.
> Do I replace it with all its elements or is there a plan to move it to
> gmbal, so that it becomes a type that can be used outside GF source tree?
For this CallFlowInfo type, you need to implement ||
|org.glassfish.external.statistics.Statistic, and optionally
||org.glassfish.external.statistics.Stats.|
Please see Sreeni's write-up,
http://appserver.sfbay.sun.com/Wiki.jsp?page=Monitorig_stat_usage, for
help on how to create module specific statistics.
Here's the link to the API which is also linked from the write-up:
http://kenai.com/projects/gmbal/sources/gf_common/show/src/org/glassfish/external/statistics
>
> Q3. Can I separate @ManagedAttribute methods from @ProbeListener, so
> that they are in 2 different classes?
yes I believe you should be able to.
>
> Q4. How can I pre-set which @ProbeListener (or Statistic instance) is
> being monitored on level LOW vs. HIGH?
>
> thank you,
> -marina
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>