geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viet Hung Nguyen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-3441) Server monitoring and management
Date Tue, 25 Sep 2007 20:49:50 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Viet Hung Nguyen updated GERONIMO-3441:
---------------------------------------

    Attachment: stats.patch
                MRC-server.zip

Erik and I have made a lot of changes to our initial approach. We are now dealing exclusively
with JSR 77 stats. The attached patch, will surface Jetty Container stats so that the collecting
agent (which is in MRC-server.zip) can collect both tomcat or jetty stats. So far, this collecting
agent will work on any container and, by default, will choose to collect and save an ongoing
history of Container and Connector stats (if they are provided). There is also the added feature
of allowing the client (in this case, an Admin) to add/remove other JSR-77 stats from a list
of available mbeans.

> 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-server.zip, MRC.zip, screenshot1.jpg, screenshot2.jpg, stats.patch,
statsportlet.zip
>
>
> 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.


Mime
View raw message