Bug 1024533 - Metric chart's low and peak value is using wrong data (integer metrics return decimals)
Metric chart's low and peak value is using wrong data (integer metrics return...
Product: JBoss Operations Network
Classification: JBoss
Component: Monitoring -- Other (Show other bugs)
JON 3.1.2
Unspecified Unspecified
unspecified Severity urgent
: ---
: JON 3.2.0
Assigned To: Mike Thompson
Mike Foley
Depends On: 870561
  Show dependency treegraph
Reported: 2013-10-29 17:05 EDT by Larry O'Leary
Modified: 2013-11-05 09:52 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-11-05 09:52:20 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Metric graph page showing low value of 2 and peak of 3 (76.67 KB, image/png)
2013-10-29 17:20 EDT, Larry O'Leary
no flags Details
Metric chart page showing low value of 2.05?? and peak of 2.95?? (54.27 KB, image/png)
2013-10-29 17:21 EDT, Larry O'Leary
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 240563 None None None Never

  None (edit)
Description Larry O'Leary 2013-10-29 17:05:26 EDT
Description of problem:
When viewing the metric graph for a past period (such as from a couple weeks ago) we seem to be displaying the min and max values incorrectly for the specified period. This is very evident when working with metrics that are always of integer values such as an EAP 5 datasource's connection count. This metric can only be an integer. 

However, when reviewing data from a period from more then a couple weeks ago, it minimum and maximum values are displayed as fractions even though the data stored in the 1h, 6h, and 1d tables all clearly show that min and max values are 0 and 1. 

This actually may be a regression as this issue (or similar issue) had already been identified in bug 870561 and was supposedly fixed in JON 3.1.2. However, it is now obvious that this may not have been completely fixed.

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

How reproducible:

Steps to Reproduce:
1. Wait for the r00-r14, 1h, 6h, and 1d tables to be populated for the RHQ server's NoTxRHQDS total connections metric. 

   Please note that this will take 15 or more days. It may not be necessary to wait this long but the testing has revealed that this issue seems to happen when multiple metric tables are involved. It is not clear to which tables are actually involved.

2. View the RHQ server's NoTxRHQDS monitoring graphs page.,
3. Set the view range to be a week or so in the past and to be for an 8 hour period in where the metric was collected once every 20 minutes.
4. Take note of the low and peak values for the total connections graph.
5. View the RHQ server's NoTxRHQDS monitoring tables page and take note of the total connections metric minimum and maximum values.
6. Select the table row for the total connections metric and click the "chart selected metrics" button.
7. Take note of the Peak line and Low line on the total connections metric chart.

Actual results:
Low and Peak line on metric graph are aligned with a decimal (non-integer) on the y axis of the chart. These values do not match that of low and minimum or peak and maximum values displayed on the metric graph and table respectively.

Expected results:
All values should be the same and be an integer value.
Comment 1 Larry O'Leary 2013-10-29 17:20:14 EDT
Created attachment 817192 [details]
Metric graph page showing low value of 2 and peak of 3
Comment 2 Larry O'Leary 2013-10-29 17:21:25 EDT
Created attachment 817193 [details]
Metric chart page showing low value of 2.05?? and peak of 2.95??

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