| Summary: | Hawkular metrics clipped if initial Y-axis insufficient for subsequent resource use | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Justin Pierce <jupierce> | ||||
| Component: | Management Console | Assignee: | Jessica Forrester <jforrest> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.x | CC: | aos-bugs, jokerman, mmccomas | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-10-19 18:43:25 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 1386708 *** |
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: