Bug 1064110 - Make metrics aggregation settings configurable
Summary: Make metrics aggregation settings configurable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server, Plugins, Monitoring, Storage Node
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: ---,RHQ 4.10
Assignee: John Sanda
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-12 03:29 UTC by John Sanda
Modified: 2014-04-23 12:31 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-23 12:31:39 UTC
Embargoed:


Attachments (Terms of Use)

Description John Sanda 2014-02-12 03:29:11 UTC
Description of problem:
This is directly related to the work done for bug 1009945. There are some settings that can tune the performance of metrics aggregation. There is a brief design doc[1] that discusses these settings. The settings need to be configurable through  the appropriate managed resource when the RHQ Server is committed into inventory as well being configurable when the server is not managed.

[1] https://docs.jboss.org/author/display/RHQ/Metrics+Aggregation+Performance+Tuning


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-02-12 03:37:46 UTC
Aggregation settings can be configured in two ways. The first is by directly in    editing the properties in rhq-server.properties. Doing so requires a server
restart for changes to take effect. The second way is through the Measurement
Subsystem resource which is defined in the rhq-server agent plugin. When the settings are modified through the resource configuration, changes are applied dynamically at runtime and do not require a server restart.

master commit hash: a7d46c9

Comment 2 Heiko W. Rupp 2014-04-23 12:31:39 UTC
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.


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