Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1362390 - [RFE] Show Storage/Memory/CPU utilization numbers when hovering above the utilization square
Summary: [RFE] Show Storage/Memory/CPU utilization numbers when hovering above the uti...
Keywords:
Status: NEW
Alias: None
Product: ovirt-engine-dashboard
Classification: oVirt
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Vojtech Szocs
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-02 06:21 UTC by Barak Korren
Modified: 2018-01-04 09:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: UX
oourfali: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Barak Korren 2016-08-02 06:21:09 UTC
The bottom part of the dashboard screen shows colored squares indicating per-cluster CPU/Memory utilization and per-domain storage utilization.

Hovering with the mouse tell you which cluster/domain does the square represent. It would be great if it could also show you the utilization amounts for taht cluster/domain that cause the square to be colored as it is.

Comment 1 Vojtech Szocs 2016-08-02 17:22:10 UTC
Heat map blocks are colored according to percentage value sent by server.

Should we show that percentage as part of the tooltip? Do we need to show any other relevant info in the tooltip, besides object's name + percentage used?

Comment 2 Barak Korren 2016-08-03 06:55:04 UTC
I'd prefer concrete data on the tooltip as opposed percentage - if it red I already know its in the above 90 percentile, I'm hovering over it because I want concrete data - do I have a few MBs left or a few TBs?

Showing percentile for storage and RAM utilization is overrated - a 90% full petabyte storage is not the same as a 90% full 100GB storage...

Comment 3 Vojtech Szocs 2016-08-05 15:48:57 UTC
(In reply to Barak Korren from comment #2)
> I'd prefer concrete data on the tooltip as opposed percentage - if it red I
> already know its in the above 90 percentile, I'm hovering over it because I
> want concrete data - do I have a few MBs left or a few TBs?

Agreed, makes sense.

Do you have an idea/suggestion on how should the tooltip look like when hovering CPU/Memory/Storage heat map blocks? (can be different kind of tooltip for each)

Comment 4 Barak Korren 2016-08-07 08:08:56 UTC
> Do you have an idea/suggestion on how should the tooltip look like when 
> hovering CPU/Memory/Storage heat map blocks? (can be different kind of 
> tooltip for each)

Please note that carefully tuning textual messages is out of me area of expertise, so I'm hoping someone more qualified will have a look at this, but here are my suggestions:

CPU:
  "foo_cluster: 68% used"
Memory:
  if > 50% used: "foo_cluster: 123GB of 762GB free"
  if < 50% used: "foo_cluster: 50GB of 762GB used"
Storage (similar logic to memory but maybe more meaningful here):
  if > 50% used: "bar_domain: 158GB of 4TB free"
  if < 50% used: "bar_domain: 512GB of 4TB used"

Where:
- foo_cluster is the name of the cluster we're hovering above
- bar_domain is the name of the domain we're hovering above

Note the alternating usage of free or used. The idea is to let unit scaling intelligently show the more useful data. If we just show used for example we can end up showing "3.8TB of 4TB used" which is far less meaningful IMO.

WRT using 50% as the decision point - I'm not 100% sure about that. The heat map uses 65% as the lowest point of reference, so maybe it will be better in this case.

Comment 5 Vojtech Szocs 2016-08-09 18:18:37 UTC
(In reply to Barak Korren from comment #4)
> Note the alternating usage of free or used. The idea is to let unit scaling
> intelligently show the more useful data. If we just show used for example we
> can end up showing "3.8TB of 4TB used" which is far less meaningful IMO.

Sounds OK.

We already have a basic unit conversion/scaling logic in place, currently used in over-utilized dialog (shown after clicking the donut). When the value is outside (0.1, 1024) range, the unit/value will be up/down-scaled accordingly, e.g. 10000 MiB becomes 10000 / 1024 = ~9.77 GiB etc.

Unit test for that logic is here: https://gerrit.ovirt.org/gitweb?p=ovirt-engine-dashboard.git;a=blob;f=src/utils/unit-conversion-test.js;hb=HEAD

> WRT using 50% as the decision point - I'm not 100% sure about that. The heat
> map uses 65% as the lowest point of reference, so maybe it will be better in
> this case.

65% sounds more consistent with existing heat map thresholds.


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