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.188 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:mime-version:content-type;
        b=Q6xLgN+BwaE0fRnk5TkjpCtmp1W1VrC203ZXR+kJ4HjsoVHkDu65X4sUwZeVKCyRgzE8useJE1Yoz7iSfJPQXa/QgY9Y6SuOD+wJabc3x9M/MmT4wfce6Z/Wc7fPtrINZChYQXpW5fiO8wDnBjZpEmpWXvnjQ7lrPwDcFWfQ6qg=
Message-ID: <4e8584bd0709260740v2b247faj8e4ca705d3006cb5@mail.gmail.com>
Date: Wed, 26 Sep 2007 10:40:40 -0400
From: "Erik B. Craig" <ginemesis@gmail.com>
Reply-To: erik.craig@gmail.com
To: dev@geronimo.apache.org
Subject: [UPDATE] Server monitoring and Management plugin
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3307_23559285.1190817640043"

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

Greetings,

After a round of improvements to the monitoring and management plugin that
Viet an I have been working on (
https://issues.apache.org/jira/browse/GERONIMO-3441), we felt it was time to
update everyone on where things are at, and hopefully get a good deal of
feedback and perhaps a feel for the direction everyone thinks would be best
for this.

Since the last time we brought it to the dev list, the method in which data
is collected has been changed to utilize the JSR77 defined statistics.
Currently we have implemented this for the Tomcat connectors
'TomcatWebConnector', 'TomcatWebSSLConnector', and 'TomcatAJPConnector'.
This information is still having 'snapshots' taken, and is then stored
locally at a set interval (now defined in a configuration file) in an XML
file. There are still some issues revolving around surfacing the equivalent
statistics for Jetty (We have tomcat CONNECTORS, but jetty CONTAINERS),
largely due to geronimo losing a handle on them since jetty6, but it is
being worked on. In addition to Jetty, we're also looking at getting MEJB
stats surfaced and tracked very soon down the road... and if anyone has any
other suggestions for what you think should be able to be collected, it
would be greatly appreciated.

In addition to using JSR77 on the mrc-server component, there are a number
of other improvements, including
* Archiving of snapshot data in a zip file every month - prevent the single
active file from getting too large
* Ability to start/stop the statistics collection thread
* Specify the duration between snapshots
* Ability to modify mbean attributes
* Ability to add mbeans to track in the snapshot process

As far as the client side of things goes...

The plugin has been updated to be deployable on the latest iteration of the
plugable console Paul has been working on, and is working fully on the
latest 2.1 trunk with the plugable console deployed. It is also now doing
page generation through JSPs from the portlet, where as previously it was
simple line prints to the http response. The graphing is now far more
dynamic, and able to accept any time frame (in minutes) from
2*snapshotduration up to however high you can count (or fit into an integer,
whichever comes first). If there is not enough snapshot data to generate the
requested graph, 'older' data will be inserted with values of 0. If there
are gaps in the snapshots (I.E. the snapshot time of element 1 vs. element 2
is greater than the snapshot duration), the client will fill in dummy data
between the two, so that the time frame and stamps on the generated graph is
accurate. (To be further improved to indicate gaps via highlighting on the
graphs).

In addition to this, determining exactly 'what' is being graphed is now
dynamically done depending on what is being collected on the server side.
This will further be improved through a configuration page and file on the
client side, that will allow enabling or disabling of graphs for statistics
being collected on the server side , as well as configuring exactly how they
are displayed (color, axis labels, size, etc).

For some more information on the current status, check out the jira link
above, or the wiki page here
http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service

Again - all feedback, questions, suggestions would be greatly appreciated

On a side note - would it be possible to get an iteration of this stuff
checked into either sandbox of the plugins directory? It would certainly
make things much easier for collaboration and revision control =)

Thanks,

-- 
Erik B. Craig

------=_Part_3307_23559285.1190817640043
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Greetings,<br><br>After a round of improvements to the monitoring and manag=
ement plugin that Viet an I have been working on (<a href=3D"https://issues=
.apache.org/jira/browse/GERONIMO-3441">https://issues.apache.org/jira/brows=
e/GERONIMO-3441
</a>), we felt it was time to update everyone on where things are at, and h=
opefully get a good deal of feedback and perhaps a feel for the direction e=
veryone thinks would be best for this.<br clear=3D"all"><br>Since the last =
time we brought it to the dev list, the method in which data is collected h=
as been changed to utilize the JSR77 defined statistics. Currently we have =
implemented this for the Tomcat connectors &#39;TomcatWebConnector&#39;, &#=
39;TomcatWebSSLConnector&#39;, and &#39;TomcatAJPConnector&#39;. This infor=
mation is still having &#39;snapshots&#39; taken, and is then stored locall=
y at a set interval (now defined in a configuration file) in an XML file. T=
here are still some issues revolving around surfacing the equivalent statis=
tics for Jetty (We have tomcat CONNECTORS, but jetty CONTAINERS), largely d=
ue to geronimo losing a handle on them since jetty6, but it is being worked=
 on. In addition to Jetty, we&#39;re also looking at getting MEJB stats sur=
faced and tracked very soon down the road... and if anyone has any other su=
ggestions for what you think should be able to be collected, it would be gr=
eatly appreciated.=20
<br><br>In addition to using JSR77 on the mrc-server component, there are a=
 number of other improvements, including<br>* Archiving of snapshot data in=
 a zip file every month - prevent the single active file from getting too l=
arge
<br>* Ability to start/stop the statistics collection thread<br>* Specify t=
he duration between snapshots<br>* Ability to modify mbean attributes<br>* =
Ability to add mbeans to track in the snapshot process<br><br>As far as the=
 client side of things goes...
<br><br>The plugin has been updated to be deployable on the latest iteratio=
n of the plugable console Paul has been working on, and is working fully on=
 the latest 2.1 trunk with the plugable console deployed. It is also now do=
ing page generation through JSPs from the portlet, where as previously it w=
as simple line prints to the http response. The graphing is now far more dy=
namic, and able to accept any time frame (in minutes) from 2*snapshotdurati=
on up to however high you can count (or fit into an integer, whichever come=
s first). If there is not enough snapshot data to generate the requested gr=
aph, &#39;older&#39; data will be inserted with values of 0. If there are g=
aps in the snapshots (
I.E. the snapshot time of element 1 vs. element 2 is greater than the snaps=
hot duration), the client will fill in dummy data between the two, so that =
the time frame and stamps on the generated graph is accurate. (To be furthe=
r improved to indicate gaps via highlighting on the graphs).
<br><br>In addition to this, determining exactly &#39;what&#39; is being gr=
aphed is now dynamically done depending on what is being collected on the s=
erver side. This will further be improved through a configuration page and =
file on the client side, that will allow enabling or disabling of graphs fo=
r statistics being collected on the server side , as well as configuring ex=
actly how they are displayed (color, axis labels, size, etc).
<br><br>For some more information on the current status, check out the jira=
 link above, or the wiki page here<br><a href=3D"http://cwiki.apache.org/co=
nfluence/display/GMOxDEV/Monitoring+and+Management+Service">http://cwiki.ap=
ache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service
</a><br><br>Again - all feedback, questions, suggestions would be greatly a=
ppreciated<br><br>On a side note - would it be possible to get an iteration=
 of this stuff checked into either sandbox of the plugins directory? It wou=
ld certainly make things much easier for collaboration and revision control=
 =3D)
<br><br>Thanks,<br><br>-- <br>Erik B. Craig

------=_Part_3307_23559285.1190817640043--