[
https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik B. Craig updated GERONIMO-3441:
------------------------------------
Attachment: mrc-client.zip
Updated to exploit the new features we've implemented in the mrc-server side.
Now utilizing the JSR77 stats that are being tracked, as well as is now far
more dynamic than previously. Currently able to display any timeframe from
(2*snapshotduration) all the way to indefinite... as passed as a time value in
minutes in the JSP.
The client side will fill in 'gaps' in the snapshot data with 'dummy data'
(zeros) to account for periods in which the snapshot thread was not running of
the server was stopped. It will also place dummy data on the left side of the
graph in the instance where there is not enough data to generate the desired
timeframe, so that the graph is still as expected. This will be improved to
indicate periods where the stats collection was not functional with some
highlighting.
The client side is now fully dynamic in retrieving what stats to graph from the
server side, and can display based on selective mbeans.
In the future this functionality will be further extended through the use of a
configuration page/file on the client side to manipulate the axis labels for
specific graphs, as well as enable or disable the drawing of specific graphs
without disabling the statistics collection for that piece of data
The client side has also been updated to be deployable on Paul's most recent
plugable admin console on current 2.1 trunk.
> Server monitoring and management
> --------------------------------
>
> Key: GERONIMO-3441
> URL: https://issues.apache.org/jira/browse/GERONIMO-3441
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: general
> Affects Versions: 2.1
> Environment: All
> Reporter: Erik B. Craig
> Assignee: Erik B. Craig
> Attachments: mrc-client.zip, MRC-server.zip, screenshot1.jpg,
> screenshot2.jpg, stats.patch
>
>
> Currently, there is not a good way of surfacing Geronimo's server information
> so that an administrator can monitor the server's status. The architecture of
> using MBeans is established, but not fully exploited. This enhancement will
> take advantage of what Geronimo currently offers and extend it so that a
> server can tap into a cluster of servers and extract information from
> specific Geronimo servers or even aggregates of Geronimo servers.
> The goal is to have one machine be able to reach out to all Geronimo servers
> in order to fetch data or even alter their state. This will be especially
> useful in the case of someone having to monitor a large number of Geronimo
> servers.
> Viet Nguyen and myself have completed a bit of framework towards this goal,
> to be attached to this jira
> In-depth information can be found in the confluence wiki here
> http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
