geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik B. Craig" <>
Subject Re: [DISCUSS] Moving the Monitoring Plugin Into Trunk
Date Thu, 06 Dec 2007 01:21:52 GMT
You mentioned that the collecting agent running within the same jvm  
(I.E. under a Geronimo instance being monitored as a plugin) is an  
issue due to resource consumption... however I am unsure what a good  
alternative approach would be? Are you suggesting we have a separate  
instance of G to monitor a target instance? Or are you suggesting that  
the mrc-server be a standalone java app that runs in it's own JVM?

Currently the graph builder will plot any data being grabbed as  
snapshots in any method defined by the user. In the current graph  
creation page, the user has the option to differentiate between raw  
count vs. count/time or even count/some other count. There are a lot  
of options configurable by the user.

Additionally... do you have an example of the graphs for  
TimeStatistics or BoundedRangeStatistics being wrong/how they are wrong?

On Dec 5, 2007, at 7:29 PM, Anita Kulshreshtha wrote:

> Viet,
>   Thanks for working on the monitoring console. A lot still remains to
> be done. There are architectural issues which need to be addressed:
>    Currently the agent (aka mrc-server) needs to reside in same jvm as
> the server being monitored. It consumes significant DB resources.
>    The Graph builder plots CountStatistics correctly. It does not
> provide a way (minor point) to choose/plot both the raw count and the
> throughput, i.e. count/sec. The graphs for TimeStatistics and
> BoundedRangeStatistics are wrong. This is a serious shortcoming. I
> would like it to be fixed before we can talk about releasing it.
> Thanks
> Anita
> --- Viet Nguyen <> wrote:
>> Hi All,
>> There has been a lot of work done on the monitoring plugin lately. I
>> think it is now time to move it from sandbox into trunk, in time for
>> the 2.1 release. I am unsure
>> of the timeline for 2.1, but I feel as though the monitoring plugin
>> should be moved to trunk around this time, so that the little kinks
>> can be worked out before it is
>> too late for the release. Erik and I have worked together along with
>> the help of many others to provide a monitoring collecting agent and
>> monitoring portlet.
>> To briefly go over what the monitoring plugin can do:
>> -monitor multiple servers
>> -securely connects to remote servers that are monitored (via MEJB and
>> encryption of the password using Geronimo's EncryptionManager)
>> -keeps an on going history of user-chosen statistics
>> -provides the ability to view current and past statistics
>> -customizable graphs (e.g. I can choose which stats I want to graph,
>> and much more)
>> -the ability to group certain graphs together into what we call a
>> "view." The idea is to allow an administrator to view only those
>> graphs that he cares about...all in one place!
>> -editable server, graphs, and views option
>> -provides the ability to keep track of any mbean that is declared as
>> a
>> StatisticsProvider
>> -administrator can custom define the elapsed time period before each
>> snapshot is taken
>> -everything is packaged into plugins (separate plugins and a bundled
>> plugin with both pieces), so deploying is made easier
>> I hope that some of you can take some time to test out the plugin
>> which can be pulled from sandbox at
>> and
>> provide
>> some feedback. If there are no objections, I hope that a committer
>> can
>> soon move the monitoring plugin into trunk. One of the new features
>> that I would like to see listed
>> for the 2.1 release is this monitoring plugin. I believe it will
>> attract a lot of attention and users.
>> Thanks,
>> Viet
> ____________________________________________________________________________________
> Looking for last minute shopping deals?
> Find them fast with Yahoo! Search.

View raw message