Bug 1386752 - Hawkular metrics clipped if initial Y-axis insufficient for subsequent resource use
Summary: Hawkular metrics clipped if initial Y-axis insufficient for subsequent resour...
Keywords:
Status: CLOSED DUPLICATE of bug 1386708
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Management Console
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 14:49 UTC by Justin Pierce
Modified: 2016-10-19 18:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-19 18:43:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screen shot showing clipped network report (24.44 KB, image/png)
2016-10-19 14:49 UTC, Justin Pierce
no flags Details

Description Justin Pierce 2016-10-19 14:49:31 UTC
Created attachment 1212180 [details]
screen shot showing clipped network report

Description of problem:
Metric graphs for my pod (e.g. memory/cpu/network) automatically scale their Y-axis for past data when I load the Overview page. However, if I stay on the overview page and, through a stress test, increase the utilization of one of these resources beyond the maximum value of the Y-axis, the visual spike in utilization will be clipped in subsequent updates to the graph. 

The Y-Axis does not adjust its scaling to accommodate the incoming data. 

Version-Release number of selected component (if applicable):
3.3 Metrics
Firefox 47
Fedora

How reproducible:
100%

Steps to Reproduce:
1. Create a new pod (e.g. ruby-hello-world).
2. Load the web-console overview page with metrics enabled.
3. Create an artificial load on the ruby application for several minutes.
4. Without ever reloading the page, view the graph on the overview page.


Actual results:
The graph will clipped and not display the full extent of the resource utilization.

Expected results:
The graph will scale its Y-axis appropriately to accommodate incoming data.

Additional info:

Comment 1 Dan McPherson 2016-10-19 18:43:25 UTC

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


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