You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Erik B. Craig (JIRA)" <ji...@apache.org> on 2007/08/23 23:32:31 UTC
[jira] Created: (GERONIMO-3441) Server monitoring and management
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
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viet Hung Nguyen updated GERONIMO-3441:
---------------------------------------
Attachment: MRC.zip
I have attached the MRC gbean which will reside on the server(s) to be monitored. This Gbean provides a gateway for the management server (the stuff that Erik is working on) to query and even make changes to the existing components on whatever server that the MRC gbean is monitoring.
This version of the MRC gbean has also enabled monthly archiving of the server's information.
> 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.zip, screenshot1.jpg, screenshot2.jpg, 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig updated GERONIMO-3441:
------------------------------------
Attachment: statsportlet.zip
User interface (portlet intended for plugable admin console) component of the set.
To implement, you need 2.x minimal assembly (tomcat) running, with the console from
https://svn.apache.org/repos/asf/geronimo/plugins/console/ installed, as well as pluto from
https://svn.apache.org/repos/asf/geronimo/plugins/pluto/ installed.
In addition to this, the tomcat-dojo plugin must also be installed, as well as the MRC component that collects the statistics/forwards to this client.
Once all this requirements are met, this zip can be extracted, and compiled with mvn install.
All that must be done then is to do a deploy of the .war created in the target directory from within the plugable admin console.
On first load, a stats collection thread will be started with a snapshot interval of 60 seconds. The portlet is currently hardcoded to generate 15-minute graphs for all of the data tracked from tomcat.
> 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.zip, screenshot1.jpg, screenshot2.jpg, 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ 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 contain proper license headers, LICENSE.txt and NOTICE.txt
> 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.
[jira] Assigned: (GERONIMO-3441) Server monitoring and management
Posted by "Anita Kulshreshtha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anita Kulshreshtha reassigned GERONIMO-3441:
--------------------------------------------
Assignee: Anita Kulshreshtha (was: Erik B. Craig)
> 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: Anita Kulshreshtha
> Attachments: mrc-client.zip, mrc-server.zip, mrc.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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viet Hung Nguyen updated GERONIMO-3441:
---------------------------------------
Attachment: (was: MRC.zip)
> 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, 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig updated GERONIMO-3441:
------------------------------------
Attachment: (was: statsportlet.zip)
> 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, 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig updated GERONIMO-3441:
------------------------------------
Description:
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
was:
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
> 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
>
> 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig updated GERONIMO-3441:
------------------------------------
Attachment: (was: mrc-client.zip)
> 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, 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ 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-server.zip
Updated to include proper license headers, LICENSE.txt, NOTICE.txt
> 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viet Hung Nguyen updated GERONIMO-3441:
---------------------------------------
Attachment: (was: MRC-server.zip)
> 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.
[jira] Issue Comment Edited: (GERONIMO-3441) Server monitoring and
management
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522276 ]
vhnguyen edited comment on GERONIMO-3441 at 8/23/07 2:43 PM:
---------------------------------------------------------------------
I have attached the MRC gbean which will reside on the server(s) to be monitored. This Gbean provides a gateway for the management server (the stuff that Erik is working on) to query and even make changes to the existing components on whatever server that the MRC gbean is monitoring.
This version of the MRC gbean has also enabled monthly archiving of the server's information.
Also, please read the 'readme.txt' file for information on how to compile and deploy this gbean.
was (Author: vhnguyen):
I have attached the MRC gbean which will reside on the server(s) to be monitored. This Gbean provides a gateway for the management server (the stuff that Erik is working on) to query and even make changes to the existing components on whatever server that the MRC gbean is monitoring.
This version of the MRC gbean has also enabled monthly archiving of the server's information.
> 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.zip, screenshot1.jpg, screenshot2.jpg, 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.
[jira] Commented: (GERONIMO-3441) Server monitoring and management
Posted by "Anita Kulshreshtha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530421 ]
Anita Kulshreshtha commented on GERONIMO-3441:
----------------------------------------------
I have few more comments/questions:
- Where are the The startTime and lastSampleTime for each statistic being set/updated? The startTime is the time the statistic collection was started. The resetStats() sets this time to current time. You might need to initialize Jetty's statistics collection mechanism during resetStats.
- Where is statisticsProvider attribute being set to true for JettyContainer?
- Does tomcat module compile with the stats.patch? Does Jetty provide per connector statistics?
Could you please resubmit stats.patch with above changes?
> 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, 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.
[jira] Closed: (GERONIMO-3441) Server monitoring and management
Posted by "Anita Kulshreshtha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anita Kulshreshtha closed GERONIMO-3441.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.1
rev. 580468 - Initial check in to sandbox
> 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: Anita Kulshreshtha
> Fix For: 2.1
>
> Attachments: mrc-client.zip, mrc-server.zip, mrc.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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ 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
I have added the lastSampleTime and startTime field for each statistic. Also, the statisticsProvider attribute was already set to true, so it is not present in the patch, but it is there when I view the mbean from jconsole.
This patch also exposes the Jetty Connector stats in addition to the Jetty Container stats. I have tested this patch on the latest trunk and both tomcat and jetty works fine.
If someone could review the patch along with the MRC plugins, it will be great to get this into sandbox.
> 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig updated GERONIMO-3441:
------------------------------------
Attachment: screenshot2.jpg
Screenshot2, first iteration of console UI portlet
> 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: screenshot1.jpg, screenshot2.jpg
>
>
> 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ 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.zip
I have created a combined package with a pom to handle building both the client and the server, everything has proper License information, as well as notice information (both the files and in the headers of all source files). The directory structure is completely setup for import into svn as geronimo/sandbox/svn (has the branches/tags/trunk directories created, with content in the trunk only currently)
> 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, mrc.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.
[jira] Commented: (GERONIMO-3441) Server monitoring and management
Posted by "Anita Kulshreshtha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522323 ]
Anita Kulshreshtha commented on GERONIMO-3441:
----------------------------------------------
Nice work! A graphical representation of the stats will be a good thing to have. However, I would like us to use JSR77 for monitoring and management. A good starting point will be to use J2EEManaged Objects and its StatisticsProvider model. Thus every time a new thing has to be monitored, writing a new "controller" is not required. The current design requires writing a new controller. The controller should collect statistics in a components agnostics way. The management plugin will be able to extract all the information from it using JSR77 Stats model. If you have not already seen, the JMXViewer in admin console has a Stats tab to display statistics in JSR77 format for all managed objects that are statistics providers. Currently only tomcat's connector and deployed web modules are statistics provider. We need to do the same for Jetty.
> 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.zip, screenshot1.jpg, screenshot2.jpg, 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viet Hung Nguyen updated GERONIMO-3441:
---------------------------------------
Attachment: (was: stats.patch)
> 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
>
>
> 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig updated GERONIMO-3441:
------------------------------------
Attachment: screenshot1.jpg
Screenshot1, showing first iteration of the console plugin UI component
> 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: screenshot1.jpg, screenshot2.jpg
>
>
> 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.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ 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.