[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly

2009-05-28 Thread David Jencks (JIRA)

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

David Jencks updated GERONIMO-3685:
---

Fix Version/s: (was: 2.2)
   Wish List

I wish I understood these statistics.  Doesn't look like its happening for 2.2

 Monitoring Console should display TimeStatistics and BoundedRangeStatistics 
 correctly
 -

 Key: GERONIMO-3685
 URL: https://issues.apache.org/jira/browse/GERONIMO-3685
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: All
Reporter: Anita Kulshreshtha
Priority: Critical
 Fix For: Wish List


  . The Monitoring Console (MC) should display TimeStatistics and 
 BoundedRangeStatistics as a single value. 
 For example JVM Heap  or RequestTime or openConnections with a single 
 link  for graph.
 . A band-aid solution to displaying TimeStatistics and 
 BoundedRangeStatistics, and RangeStatistics is to add a field 
 'StatisticsType' to activeDB.
 and graph 'totalTime/count' for Timestatistics and 'current' for 
 BoundedRangeStatistics, RangeStatistics. 
 . The graph builder recomputes min, max and avg. It is wasteful but 
 acceptable for now.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly

2008-02-25 Thread Erik B. Craig (JIRA)

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

Erik B. Craig updated GERONIMO-3685:


Fix Version/s: 2.2

 Monitoring Console should display TimeStatistics and BoundedRangeStatistics 
 correctly
 -

 Key: GERONIMO-3685
 URL: https://issues.apache.org/jira/browse/GERONIMO-3685
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
 Environment: All
Reporter: Anita Kulshreshtha
Priority: Critical
 Fix For: 2.1.1, 2.2


  . The Monitoring Console (MC) should display TimeStatistics and 
 BoundedRangeStatistics as a single value. 
 For example JVM Heap  or RequestTime or openConnections with a single 
 link  for graph.
 . A band-aid solution to displaying TimeStatistics and 
 BoundedRangeStatistics, and RangeStatistics is to add a field 
 'StatisticsType' to activeDB.
 and graph 'totalTime/count' for Timestatistics and 'current' for 
 BoundedRangeStatistics, RangeStatistics. 
 . The graph builder recomputes min, max and avg. It is wasteful but 
 acceptable for now.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly

2008-02-25 Thread Erik B. Craig (JIRA)

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

Erik B. Craig updated GERONIMO-3685:


Affects Version/s: 2.2
   2.1.1
   2.1
Fix Version/s: (was: 2.1.1)

 Monitoring Console should display TimeStatistics and BoundedRangeStatistics 
 correctly
 -

 Key: GERONIMO-3685
 URL: https://issues.apache.org/jira/browse/GERONIMO-3685
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: All
Reporter: Anita Kulshreshtha
Priority: Critical
 Fix For: 2.2


  . The Monitoring Console (MC) should display TimeStatistics and 
 BoundedRangeStatistics as a single value. 
 For example JVM Heap  or RequestTime or openConnections with a single 
 link  for graph.
 . A band-aid solution to displaying TimeStatistics and 
 BoundedRangeStatistics, and RangeStatistics is to add a field 
 'StatisticsType' to activeDB.
 and graph 'totalTime/count' for Timestatistics and 'current' for 
 BoundedRangeStatistics, RangeStatistics. 
 . The graph builder recomputes min, max and avg. It is wasteful but 
 acceptable for now.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly

2008-02-01 Thread Kevan Miller (JIRA)

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

Kevan Miller updated GERONIMO-3685:
---

Fix Version/s: (was: 2.1)
   2.1.1

Assume we're ok, as is. If someone, could answer anita's question, would be good

 Monitoring Console should display TimeStatistics and BoundedRangeStatistics 
 correctly
 -

 Key: GERONIMO-3685
 URL: https://issues.apache.org/jira/browse/GERONIMO-3685
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
 Environment: All
Reporter: Anita Kulshreshtha
Priority: Critical
 Fix For: 2.1.1


  . The Monitoring Console (MC) should display TimeStatistics and 
 BoundedRangeStatistics as a single value. 
 For example JVM Heap  or RequestTime or openConnections with a single 
 link  for graph.
 . A band-aid solution to displaying TimeStatistics and 
 BoundedRangeStatistics, and RangeStatistics is to add a field 
 'StatisticsType' to activeDB.
 and graph 'totalTime/count' for Timestatistics and 'current' for 
 BoundedRangeStatistics, RangeStatistics. 
 . The graph builder recomputes min, max and avg. It is wasteful but 
 acceptable for now.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly

2007-12-07 Thread Anita Kulshreshtha (JIRA)

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

Anita Kulshreshtha updated GERONIMO-3685:
-

Description: 
 . The Monitoring Console (MC) should display TimeStatistics and 
BoundedRangeStatistics as a single value. 
For example JVM Heap  or RequestTime or openConnections with a single link  
for graph.
. A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, 
and RangeStatistics is to add a field 'StatisticsType' to activeDB.
and graph 'totalTime/count' for Timestatistics and 'current' for 
BoundedRangeStatistics, RangeStatistics. 
. The graph builder recomputes min, max and avg. It is wasteful but acceptable 
for now.  

  was:
 . The Monitoring Console (MC) should display TimeStatistics and 
BoundedRangeStatistics as a single value. 
For example JVM Heap  or RequestTime or openConnections with a single link  
for graph.
. A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, 
and RangeStatistics is to add a field 'StatisticsType' to activeDB.
and graph 'count/totalTime' for Timestatistics and 'current' for 
BoundedRangeStatistics, RangeStatistics. 
. The graph builder recomputes min, max and avg. It is wasteful but acceptable 
for now.  


 Monitoring Console should display TimeStatistics and BoundedRangeStatistics 
 correctly
 -

 Key: GERONIMO-3685
 URL: https://issues.apache.org/jira/browse/GERONIMO-3685
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
 Environment: All
Reporter: Anita Kulshreshtha
Priority: Critical
 Fix For: 2.1


  . The Monitoring Console (MC) should display TimeStatistics and 
 BoundedRangeStatistics as a single value. 
 For example JVM Heap  or RequestTime or openConnections with a single 
 link  for graph.
 . A band-aid solution to displaying TimeStatistics and 
 BoundedRangeStatistics, and RangeStatistics is to add a field 
 'StatisticsType' to activeDB.
 and graph 'totalTime/count' for Timestatistics and 'current' for 
 BoundedRangeStatistics, RangeStatistics. 
 . The graph builder recomputes min, max and avg. It is wasteful but 
 acceptable for now.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.