Bug 1804922 - Monitoring Dashboards: k8s-resources-cluster has performance issues
Summary: Monitoring Dashboards: k8s-resources-cluster has performance issues
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On: 1795401 1880698
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-19 21:45 UTC by bpeterse
Modified: 2020-10-01 12:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1795401
Environment:
Last Closed: 2020-05-04 11:38:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4589 0 None closed [release-4.4] Bug 1804922: Improve monitoring dashboards performance 2020-10-28 00:47:14 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:38:30 UTC

Description bpeterse 2020-02-19 21:45:27 UTC 
+++ This bug was initially created as a clone of Bug #1795401 +++

Description of problem:

The monitoring/dashboards page has several performance issues.  Some of the cards do not render, and the page generally struggles.

--- Additional comment from Samuel Padgett on 2020-02-09 17:30:53 UTC ---

The cards not rendering is tracked by bug 1799907.

The pages are generally OK except for k8s-resources-cluster, which is sluggish.

--- Additional comment from  on 2020-02-19 21:44:10 UTC ---

We can rename the bug to fit that then.
Doing that before bumping to 4.5 and cloning back to 4.4.
Comment 3 Yadan Pei 2020-03-06 07:07:49 UTC 
cluster admin view Kubernetes/Compute Resources/Cluster dashboard, no sluggish switching to other dashboard or scrolling 


Verified on     4.4.0-0.nightly-2020-03-05-194612
Comment 6 errata-xmlrpc 2020-05-04 11:38:10 UTC 
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-2020:0581
Note You need to log in before you can comment on or make changes to this bug.