[jira] Commented: (GERONIMO-3441) Server monitoring and management

[Anita Kulshreshtha (JIRA)]

[ 
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] Commented: (GERONIMO-3441) Server monitoring and management

[Anita Kulshreshtha (JIRA)]

[ 
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.