Bug 1236022 - Metrics summary graph in RHQ is misleading
Summary: Metrics summary graph in RHQ is misleading
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1236021
TreeView+ depends on / blocked
 
Reported: 2015-06-26 11:22 UTC by bkramer
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description bkramer 2015-06-26 11:22:23 UTC
Description of problem:
Summary graph line will drop to 0 in between two collection point although metrics value is constant and not equal to 0. 

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

How reproducible:
Always

Steps to Reproduce:
1. Add to inventory RHQ Server resource (if it's not added already);
2. From RHQ UI -> navigate to JBossAS7 Standalone Servers -> RHQ Server resource -> Subsystems -> Connector -> datasources -> DataSource(Standalone) -> Monitoring -> Schedule
3. Change Max Pool Size collection period from 4h to 20 minutes;
4. After an hour, navigate to DataSource(Standalone) resource -> Monitoring -> Metrics -> and click on Max Pool Size to open a graph


Actual results:
Summary graph line is represented with spikes at the collection points but then this line will drop to 0 although the value of this metric is constant and equal 5 by default.

Expected results:
Graph that clearly shows metric value at the collection point and maybe a dotted line in between two collection points (that would show there was no other collections in between).

The other suggestions for the graph:

a) a bar at the measurement time (JON does this on other graphs)
b) a simple dot at the measurement time, no connecting lines
c) a dot at the measurement time, dots are connected with a line but the dot is so large that is clear that the line is based on these dots and no other measurements support the line


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