[ https://jira.jboss.org/jira/browse/EMBJOPR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Crouch moved JBMANCON-406 to EMBJOPR-57:
------------------------------------------------
Project: Embedded Jopr (was: JBoss AS 5.0 Management Console)
Key: EMBJOPR-57 (was: JBMANCON-406)
Component/s: Core Infrastructure
Web App/Integration
(was: WebApp (Seam))
Affects Version/s: 1.0
(was: 1.0 Beta 1)
> add support for per-minute metrics
> ----------------------------------
>
> Key: EMBJOPR-57
> URL: https://jira.jboss.org/jira/browse/EMBJOPR-57
> Project: Embedded Jopr
> Issue Type: Feature Request
> Components: Core Infrastructure, Web App/Integration
> Affects Versions: 1.0
> Reporter: Ian Springer
> Priority: Minor
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> We currently don't support per-minute metrics (i..e per-minute values derived from two collections of TRENDSUP/TRENDSDOWN metrics). This is primarily because the cache that the PC uses to store the last collected value for each TRENDS* metric is keyed off schedule id, and embedded does not use schedules. But it is also because if we did support per-minute metrics in embedded, it would make more sense to cache the initially collected value for each metric rather than the last collected value, which, when averaged with the current value, would produce the per minute average since the initial collection, rather than per minute value for the past <insert arbitrary time interval here>.
> Note, if we did do this, we should also consider doing an up-front collection of all metrics for all Resources in inventory at startup time, so we can cache initial values for all metrics as early as possible, rather than the user having to view a metric once in the GUI in order to initialize the per-minute cache for that metric.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira