Bug 1033338 - Disabled measurements still collected when being shown in the resource summary measurements portlet
Summary: Disabled measurements still collected when being shown in the resource summar...
Keywords:
Status: CLOSED DUPLICATE of bug 1038067
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI, Monitoring
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-21 21:33 UTC by Lukas Krejci
Modified: 2013-12-04 21:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-04 21:39:28 UTC
Embargoed:


Attachments (Terms of Use)

Description Lukas Krejci 2013-11-21 21:33:06 UTC
Description of problem:
It seems that regardless of whether a metric is enabled or disabled, when a measurement portlet on a resource summary tab shows the metric, it is collected (once on each refresh of that portlet, presumably).

Note that this can potentially generate noticeable load on the agent - if there are many (possibly expensive) metrics and many users are viewing many resources from a single agent.

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

How reproducible:
always

Steps to Reproduce:
1. Make sure that one of the metrics that is disabled on some resource is visible in the Measurements portlet on the resource summary tab
2. Let the portlet refresh a couple of times

Actual results:
Notice that both the minigraph and the detail graph (after clicking the metric) report values.


Expected results:
Disabled metric should never be collected

Additional info:

Comment 1 Mike Thompson 2013-11-22 14:59:00 UTC
Group Screens have the same issue.

Comment 2 Mike Thompson 2013-12-04 21:39:28 UTC

*** This bug has been marked as a duplicate of bug 1038067 ***

Comment 3 Mike Thompson 2013-12-04 21:40:18 UTC
@jkremser fixed this one in BZ 1038067.


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