Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=KCxyrqX5lsjynLHXHA/ZI1cibbIWQVVBeHmErgchEMiEAbiTXNJ7k5xQxFv7oJlmXQu0AH/sNJElBl9wBCXnb0ZZiJusW4V3BAAgX25byPHjDIm02dJ68NpSkxzB/H6/Uqykk+PT2AJh5kqbc9Uk0lsFbim71NHsRW/vwDNNxE0=;
Date: Wed, 5 Dec 2007 20:36:04 -0800 (PST)
From: Anita Kulshreshtha <a_kulshre@yahoo.com>
Subject: Re: [DISCUSS] Moving the Monitoring Plugin Into Trunk
To: dev@geronimo.apache.org
In-Reply-To: <675594FC-E925-4A9E-BD2B-5EAB59EAA92F@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <575548.52087.qm@web31704.mail.mud.yahoo.com>

Eric,
   For this discussion I will use MC for monitoring console (aka
client), and agent for mrc-server. It is possible to use 3 G instances
(I used this method until GERONIMO-3660). G1 with MC on remote or local
m/c, G2 with agent on local m/c, and G3 the instance to be monitored.
This is the ideal solution but will be most difficult to implement
efficiently. The advantage is that the instance to be monitored is not
corrupted in any way.
     The second option is to use 2 G instances. G1 with MC on remote or
local m/c, G2 the instance to be monitored. The agent is loaded in G2.
This is what we have now. we need to reduce DB activity. We can improve
upon this as we go. 
    The TimeSatistics has 4 values named count, max, min and totaltime.
The graph treats count as the current value of time. This is because
the information that it is a TimeStatistics is lost in the DB. All four
values appear as separate statistics, and the graph would draw each one
separately as value, min, max! The same is true for
BoundedRangeStatistics. A single graph should show all 5 values.
More inline..
   

--- "Erik B. Craig" <ecraig@apache.org> wrote:

> Anita,
> 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?

    This is a possibility too.. 
> 
> 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. 
    When I added ErrorCount and ErrorCount/sec graphs to a single view,
The other views got corrupted. This is a minor issue and can be easily
fixed.

Thanks
Anita

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


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping