Bug 1873192 - show empty state for monitoring charts when no datapoints available
Summary: show empty state for monitoring charts when no datapoints available
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Aritra Roy
QA Contact: Jaivardhan Kumar
Depends On:
TreeView+ depends on / blocked
Reported: 2020-08-27 15:21 UTC by Aritra Roy
Modified: 2020-10-27 16:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2020-10-27 16:35:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
empty state when no datapoint for chart (77.04 KB, image/png)
2020-08-27 15:21 UTC, Aritra Roy
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 6463 0 None closed Bug 1873192: show empty state in monitoring when no datapoint available 2020-09-23 10:41:46 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:35:46 UTC

Description Aritra Roy 2020-08-27 15:21:28 UTC
Created attachment 1712844 [details]
empty state when no datapoint for chart

Description of problem:
the monitoring tab shows empty charts when there are no datapoints available

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

How reproducible:

Steps to Reproduce:
1.scale a workload to zero pods
2.go to the monitoring tab of topology sidepanel

Actual results:
empty charts shown

Expected results:
empty state should be shown

Additional info:

Comment 2 Jaivardhan Kumar 2020-09-23 11:10:43 UTC
Verified on Version: 4.6.0-0.nightly-2020-09-22-213802

Comment 5 errata-xmlrpc 2020-10-27 16:35:33 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 (OpenShift Container Platform 4.6 GA Images), 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.