Bug 1034991 - Summary Last Metrics values show different values than Chart Last Metric values
Summary: Summary Last Metrics values show different values than Chart Last Metric values
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.10
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 1034852 1035443
TreeView+ depends on / blocked
 
Reported: 2013-11-26 20:04 UTC by Mike Thompson
Modified: 2014-04-23 12:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1035443 (view as bug list)
Environment:
Last Closed: 2014-04-23 12:30:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Thompson 2013-11-26 20:04:00 UTC
Description of problem:
This is one that @ahovsepy and @skondkar brought up with the summary metric last value sometimes not matching the value in the graphs.

Version-Release number of selected component (if applicable):
RHQ 4.1.0 and JON 3.2.0 ER7


How reproducible:
Depends on time range.


Steps to Reproduce:
1. Navigate to the monitor metrics tab
2. Navigate to the EAP RHQ Server
3. Observer the summary metrics value for 'Maximum Request Time'
4. click on the chart link for 'Maximum Request Time' and hover over last bar. Observer the Avg. value.

Actual results:
Depending on various time ranges these last values may or may not match.


Expected results:
The summary metric last value and chart last value (avg value on aggregate bar)should match.

Comment 1 Mike Thompson 2013-11-26 20:22:08 UTC
I have changed the code to use exactly the same date range and metric api. It was possible to use different metrics apis for the different time range types. I eliminated the variation, so that the summary last values are pulling from the same single metrics api as the charts.


Committed to master: a532e90

Comment 2 Heiko W. Rupp 2014-04-23 12:30:31 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.