David Jencks wrote: > > On Dec 5, 2007, at 4: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. > > While this might not be ideal (I don't know one way or another) does > this make it useless? I'd be in favor of getting something out with > some useful functionality now, and improving it as it gets used. >
I was going to say the same but you beat me to it. +1 with your comment...new functionality is the way to go on this. This is a huge step in the right direction and gives the user more power than they had before. It may not be perfect but it certainly is wickedly cool ;-) Anita, can you please technically show why this is not ready or should not be released? Can you explain/show where the graphs are wrong? This may help move things along. Jeff > thanks > david jencks > >> 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 <[EMAIL PROTECTED]> 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 >>> http://svn.apache.org/repos/asf/geronimo/sandbox/monitoring 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. >> http://tools.search.yahoo.com/newsearch/category.php?category=shopping
