This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 982438 - RFE: Resource and group reporting; translate per-minute to per-hour/day total
RFE: Resource and group reporting; translate per-minute to per-hour/day total
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
4.5
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-09 00:03 EDT by Elias Ross
Modified: 2013-07-09 00:03 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Elias Ross 2013-07-09 00:03:59 EDT
RHQ shows, for example, an average of requests per minute for a servlet. This is great for an administrator and can clearly show the rise and fall during the day of requests (busy times) as well as provide comparisons between two days (which day had more frequent busier times.)

For *management* reporting purposes, I'd like to see a way to translate this into per-hour and per-day *total* metrics. For example, your per-minute request rate graph may look like:

|  xx  |  xxx
| x  x | x   
|x    x|x    x
  Day 1  Day 2

over, say, a two day period. The question then is how many total requests were on day one and day two. You would like to see:

|      |  x   | 
|  x   |  x   |
|  x   |  x   |
| 1232 | 1400 | <-- estimates at the bottom

Basically it's clear here that the second day was busier.

If this were calculus, we'd be integrating over two periods, day one and day two. Obviously, since we are dealing with discreet values, it's not entirely precise, but again it's more about doing comparisons not data reconciliation.

Weekly, hourly, monthly would also be great.

Also, for a resource group, the total should be multiplied by the number of group members.

For bonus points, it would be nice to assemble multiple graphs into one. For example, see the resource request rate and the error rate.

For more bonus points, have a way to schedule sending a CSV, PDF or PNG of the results to a script that can email or publish the results for future viewing.

Note You need to log in before you can comment on or make changes to this bug.