Bug 2072797 - Metrics in Virtualization -> Overview period is not clear or configurable
Summary: Metrics in Virtualization -> Overview period is not clear or configurable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.12.0
Assignee: Tal Nisan
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On: 2102302
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-07 01:38 UTC by Germano Veit Michel
Modified: 2023-01-24 13:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-24 13:36:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 683 0 None open Bug 2072797: Add duration to top consumers card 2022-06-29 12:08:30 UTC
Red Hat Issue Tracker CNV-19705 0 None None None 2022-12-15 08:46:10 UTC
Red Hat Product Errata RHSA-2023:0408 0 None None None 2023-01-24 13:37:30 UTC

Description Germano Veit Michel 2022-04-07 01:38:03 UTC
Description of problem:

In, Virtualization -> Overview, the statistics/metrics at the bottom do not have any indication they are mostly from a 5m time period.

Please modify the UI to make the user aware of this, and/or add a button for the user to select the period.

Comment 3 Guohua Ouyang 2022-07-26 12:54:45 UTC
verified on v4.12.0-88

Comment 7 errata-xmlrpc 2023-01-24 13:36:09 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 (Important: OpenShift Virtualization 4.12.0 Images 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-2023:0408


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