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: domain of ginemesis@gmail.com
 designates 209.85.198.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
        b=H69hN0spyHenF2TW0PxhWbcKIgW4XsDoA2SA8WztK44D/ktxmHvPoxKJ12p3K9jqhOb5q7l6hKkI5tBNFkjWHM1V27RVFVYX8GT+6bYf1Ssi8DqQAw/ytyZ047FBQoyhCScp3QOjMQFKZq0MQJskw8v6i2nED11wLwwcVA5Ss2Y=
Message-ID: <4e8584bd0709071104i769d8360g31d944a89f5969e6@mail.gmail.com>
Date: Fri, 7 Sep 2007 14:04:33 -0400
From: "Erik B. Craig" <ginemesis@gmail.com>
Reply-To: erik.craig@gmail.com
To: dev@geronimo.apache.org
Subject: Re: EJB Data for monitoring
In-Reply-To: <4461D056-B1CD-4BEF-9B47-0CCB861B7CBD@visi.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1371_33015018.1189188273565"
References: <4461D056-B1CD-4BEF-9B47-0CCB861B7CBD@visi.com>

------=_Part_1371_33015018.1189188273565
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

David,

Viet and myself have started some work related to monitoring in general
through the administrative console. The work that we have laid down is
currently only exploiting some Tomcat statistics, however EJB monitoring is
definitely something we want to get added down the road to it.

To get a feel for the approach and goals we have with this project, take a
look at the wiki article on it
http://cwiki.apache.org/GMOxDEV/monitoring-and-management-service.html

as well as the Jira with the necessary files
https://issues.apache.org/jira/browse/GERONIMO-3441

Keeping in mind this is still in its infancy...
Is this something along the lines of what you are thinking for the console
part of the EJB data, and if so, would you be interested in combining
efforts so that we aren't pulling in multiple directions with monitoring
things on the server?


On 9/7/07, David Blevins <david.blevins@visi.com> wrote:
>
> So I'm thinking of adding some monitoring ability on the EJB side of
> things in the not too distant future and am wondering how things need
> to work on the Geronimo side of that picture.
>
> How does monitoring work now in the console?  Specifically some
> details on how the data is getting to where it's going (mbeans?),
> where is it being aggregated and for how long, and what technique is
> used to graph/display it?


Currently the only implemented monitoring in the console is through some
degree of real time data viewing, with maybe a min and a max value depending
on the stat, through the JMX viewer, beyond that there is no real historical
tracking of the data, which is part of what's covered in the plans I
mentioned above... as a result there is no current way of
graphing/displaying. In the current monitoring stuff, we are using Dojo
chart to generate graphs, so the graphics generation processing is done
client-side on the web browser, not on the server itself. And yes, you are
correct in part with getting the data where it's going, it is through mbeans
connected by JMX... but also the JSR77 spec is involved for what data is
pulled and such.

Also, who would want to work on the console part of the EJB data?
>
> -David
>
>


-- 
Erik B. Craig

------=_Part_1371_33015018.1189188273565
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

David,<br><br>Viet and myself have started some work related to monitoring in general through the administrative console. The work that we have laid down is currently only exploiting some Tomcat statistics, however EJB monitoring is definitely something we want to get added down the road to it.
<br><br>To get a feel for the approach and goals we have with this project, take a look at the wiki article on it<br><a href="http://cwiki.apache.org/GMOxDEV/monitoring-and-management-service.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://cwiki.apache.org/GMOxDEV/monitoring-and-management-service.html
</a><br><br>as well as the Jira with the necessary files<br><a href="https://issues.apache.org/jira/browse/GERONIMO-3441" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://issues.apache.org/jira/browse/GERONIMO-3441
</a><br><br>Keeping in mind this is still in its infancy...
<br>Is this something along the lines of what you are thinking for the console part of the EJB data, and if so, would you be interested in combining efforts so that we aren&#39;t pulling in multiple directions with monitoring things on the server?
<br><br><br><div><span class="gmail_quote">On 9/7/07, <b class="gmail_sendername">David Blevins</b> &lt;<a href="mailto:david.blevins@visi.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">david.blevins@visi.com
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So I&#39;m thinking of adding some monitoring ability on the EJB side of<br>things in the not too distant future and am wondering how things need<br>to work on the Geronimo side of that picture.<br><br>How does monitoring work now in the console?&nbsp;&nbsp;Specifically some
<br>details on how the data is getting to where it&#39;s going (mbeans?),<br>where is it being aggregated and for how long, and what technique is<br>used to graph/display it?</blockquote><div><br>Currently the only implemented monitoring in the console is through some degree of real time data viewing, with maybe a min and a max value depending on the stat, through the JMX viewer, beyond that there is no real historical tracking of the data, which is part of what&#39;s covered in the plans I mentioned above... as a result there is no current way of graphing/displaying. In the current monitoring stuff, we are using Dojo chart to generate graphs, so the graphics generation processing is done client-side on the web browser, not on the server itself. And yes, you are correct in part with getting the data where it&#39;s going, it is through mbeans connected by JMX... but also the JSR77 spec is involved for what data is pulled and such.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Also, who would want to work on the console part of the EJB data?<br><br>-David
<br><br></blockquote></div><br><br clear="all"><br>-- <br>Erik B. Craig

------=_Part_1371_33015018.1189188273565--