Created attachment 1212550 [details] Current layout screenshot Description of problem: - When a pod has a resource limit, I found the size & location of the pie-chart showing current use/limit stylistically out-of-place with the other detailed graphs. - The resource constraint pie-charts cause the vertical size of the otherwise compact/information dense timeline graphs to (likely) require scrolling. Along with the visual breaks caused by the whitespace of the pie-charts, the scrolling makes it unnecessarily difficult to systemically "take-in" the timelines all at once and see correlations. - The stylized stacked text (e.g. 7 of 512Mi Available) was also difficult to parse visually. Suggestions: - It seems the resource constraints could be visualized as a red line or shaded areas in corresponding timeline graph. - If not within the timeline graph itself, perhaps simply grouping the pie-charts into a single "Resource Constraint" row would work. - I think it would also be informative to render the "requested" resource line as a guideline for how much the deployment was anticipated to be using on average. Version-Release number of selected component (if applicable): 3.3 How reproducible: 100% - by design Steps to Reproduce: 1. Create a pod with a resource limit (e.g. jenkins ephemeral template) 2. Navigate to the metrics tab for the running pod 3. Actual results: Expected results: Additional info:
https://github.com/openshift/origin-web-console/pull/983
This has been merged into ocp and is in OCP v3.5.0.7 or newer.
Checked on OCP v3.5.0.7 Steps to verify: 1.After metrics is deployed, create pods in project, and set resource limits to one pod, the other pod has no resource limits set. 2.Check pods' metrics on web console. Actual result: 2.For pod with resource limits set, the donut chart shows on the right of the metrics sparkline; For pod without resource limits set, no donut chart shown, and the metrics sparklines are 100% width. The bug has been fixed, so move it to Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0884