Bug 1803611 - No matched metrics hint for the typed metrics in developer Query Browser
Summary: No matched metrics hint for the typed metrics in developer Query Browser
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.5.0
Assignee: Vikram Raj
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-17 03:23 UTC by Junqi Zhao
Modified: 2020-07-13 17:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:15:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5441 0 None closed Bug 1803611: show hint for the typed metrics in Metrics PromQL editor 2020-07-21 09:51:26 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:15:58 UTC

Description Junqi Zhao 2020-02-17 03:23:29 UTC
Description of problem:
Login the developer console with cluster-admin and click "Monitoring" in the left tool bar, then click "Metrics" tab, select "Custom Query" from the drop down list.
We only could type metrics in the query textarea, eg: pod:container_memory_usage_bytes:sum, there is not matching metrics appear in the list below, just Aggregation Operators and Functions could be foud.

If this is by design, we could close it.

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-02-16-205302

How reproducible:
Always

Steps to Reproduce:
1. See the description
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Gajanan More 2020-05-28 04:20:07 UTC
I have validated the bugzilla on:
Build: 4.5.0-0.nightly-2020-05-27-202943
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 7 errata-xmlrpc 2020-07-13 17:15:32 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:2409


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