+++ This bug was initially created as a clone of Bug #1140905 +++ 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:
I targeted this for 3.3.0 because it involves changes that were first introduced in RHQ 4.10, which means that they are not in JON 3.2.x but will be in JON 3.3.0.
Moving into ER05 as didn't make the ER04 cut.
Where do we stand here?
As long as the settings are configurable in some way, then I felt it was ok to retarget this for post GA. And they are configurable through the Measurement Subsystem resource configuration. I did find an issue while testing though which I addressed for ER05 with bug 1152807.
Moving to next minor/major target for future planning. @John, this does sound like it might be a bigger issue. Specifically, if you are setting the aggregation configuration on the measurement subsystem, what happens in an HA environment with multiple servers? Will they each be using their own configuration? If so, this needs to be targeted back to 3.3.z. Otherwise, future target is fine.
@John, bump? Still need a proper response for comment 5.
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121. This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days