Bug 1965984 - Console Dashboard performance leads to empty visualizations
Summary: Console Dashboard performance leads to empty visualizations
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.0
Assignee: Andrew Pickering
QA Contact: Junqi Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-31 10:08 UTC by tmicheli
Modified: 2023-03-03 09:34 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-10-18 17:32:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 9677 0 None open Bug 1965984: Monitoring dashboards: Don't load panels until they scroll into view 2021-07-29 23:50:21 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:32:17 UTC

Description tmicheli 2021-05-31 10:08:43 UTC
Description of problem:
The performance for the visualization in the console is often bad. This leads to either empty visualizations or timeout warnings. The corresponding grafana dashboards are working as expected on the same cluster and add the same time.

Version-Release number of selected component (if applicable):
* OCP 4.6.27

How reproducible:

Steps to Reproduce:

Actual results:
timeouts for the dashboards

Expected results:
No timeouts when visualizing the metrics

Additional info:

Comment 13 Junqi Zhao 2021-08-02 05:59:00 UTC
checked with 4.9.0-0.nightly-2021-08-01-132055, no empty visualizations for Console Dashboard

Comment 22 errata-xmlrpc 2021-10-18 17:32:15 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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