Bug 1952741 - Monitoring DB: after set Time Range as Custom time range, no data display
Summary: Monitoring DB: after set Time Range as Custom time range, no data display
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.8.0
Assignee: Andrew Pickering
QA Contact: hongyan li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-23 02:58 UTC by hongyan li
Modified: 2021-07-27 23:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 23:03:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screen recording (2.13 MB, application/x-matroska)
2021-04-23 02:58 UTC, hongyan li
no flags Details
screenshot (169.18 KB, image/png)
2021-04-23 03:51 UTC, hongyan li
no flags Details
screen recording (2.34 MB, application/x-matroska)
2021-04-26 08:48 UTC, hongyan li
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:03:27 UTC

Description hongyan li 2021-04-23 02:58:21 UTC
Created attachment 1774656 [details]
screen recording

Description of problem:
Monitoring DB: after set Time Range as Custom time range, no data display

Version-Release number of selected component (if applicable):
Test with PR https://github.com/openshift/console/pull/8701

How reproducible:
always

Steps to Reproduce:
1. Go to monitoring-dashboards
2. DB display well with data, we can know there is data on Apr 23 from tool tip
3. Change Time Range as Custom time range, in the pop up window with default value, click save
4. DB display no data

Actual results:


Expected results:


Additional info:
Detail see screen recorder in the attachment

Comment 1 hongyan li 2021-04-23 03:50:37 UTC
Change Time Range from Custom time range back to Last 30 minutes, display 'No datapoints found' under the first query 'etcd Request Duration - 99th Percentile'. See attached screenshot
Reload the page, everything back to normal.

Comment 2 hongyan li 2021-04-23 03:51:41 UTC
Created attachment 1774664 [details]
screenshot

Comment 3 Andrew Pickering 2021-04-23 14:02:11 UTC
Modified PR https://github.com/openshift/console/pull/8701 to fix the case where you zoom out to a custom range, then return to a preset range.

Also note that if you zoom out the graph too far (too large a time range) you can get a blank graph due the data covering too small a section of the graph to be displayed.

Comment 4 hongyan li 2021-04-26 08:47:09 UTC
Just tried today by setting up env with 'launch openshift/console#8701 aws'

Face issue
1. Go to monitoring-dashboards
2. Drag&Drop mouse on the first graph and Time Range will be changed as Custom time range
3. Click 'Custom time range' from Time Range dropdown box, in the pop up window with default value, click save
4. DB display no data

Detail see attachment

Comment 5 hongyan li 2021-04-26 08:48:46 UTC
Created attachment 1775445 [details]
screen recording

Comment 6 hongyan li 2021-04-26 09:17:56 UTC
It's expected that zoom out the graph too far (too large a time range) you can get a blank graph due the data covering too small a section of the graph to be displayed.

No issue now.

Comment 7 Andrew Pickering 2021-06-03 01:32:49 UTC
This should be fixed now that https://github.com/openshift/console/pull/8701 has merged.

Comment 9 hongyan li 2021-06-11 03:45:37 UTC
Has tested with PR, set the bug as verified

Comment 12 errata-xmlrpc 2021-07-27 23:03:04 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.8.2 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.

https://access.redhat.com/errata/RHSA-2021:2438


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