Bug 1140905 - Metrics aggregation settings should be global
Summary: Metrics aggregation settings should be global
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server, Storage Node
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.13
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1140849 1140906
TreeView+ depends on / blocked
 
Reported: 2014-09-12 02:07 UTC by John Sanda
Modified: 2022-03-31 04:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 1140906 (view as bug list)
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description John Sanda 2014-09-12 02:07:51 UTC
Description of problem:
In RHQ 4.10, we put a in place a new implementation for metrics data aggregation that addressed performance problems. With the new implementation came some settings to configure and tune the performance. This work was tracked under bug 1064110. These settings were exposed as resource configuration of the RHQ Server's measurement subsystem.

I had a lengthy discussion with Jay about where these setting should be managed. As he pointed out, since they are global, i.e., shared by all servers, they ought to be stored as system settings. 

In addition to making the aggregation settings system settings, there are some other settings we should add. Currently the starting times to look for raw, 1 hr, and 6 hr data to be aggregated is hard coded. See bug 1114202 for details. They should be configurable as well.

The second part involves additional settings that we need 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 John Sanda 2014-09-12 02:20:33 UTC
For additional settings, I forgot an important one - the metrics index page size. See bug 1135630 for details.


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