Bug 1592992

Summary: Throughput Panel in the overview dashboard needs to specify units
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Anand Paladugu <apaladug>
Component: web-admin-tendrl-monitoring-integrationAssignee: Ankush Behl <anbehl>
Status: CLOSED ERRATA QA Contact: Daniel Horák <dahorak>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: dahorak, mbukatov, nthomas, rhs-bugs, sankarshan
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: tendrl-monitoring-integration-1.6.3-6.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 07:07:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1503137    
Attachments:
Description Flags
screenshot of throughput panel without units
none
Throughput graph with units none

Description Anand Paladugu 2018-06-19 19:46:39 UTC
Description of problem:  Throughput Panel in the overview dashboard needs to specify units. 


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


How reproducible:  Open the WA UI and view the Throughput panel in the overview dashboard.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

MBPS or GBPS (as the graph represents) is reflected either in the heading "Throughput (MBPS/GBPS)" or in the panel information text.


Additional info:

Comment 2 Anand Paladugu 2018-06-19 20:35:48 UTC
In the host dashboard, network section the Throughput panel graph shows the units in Mbps.  I guess we can just use the same format here too.

Comment 3 Martin Bukatovic 2018-06-22 07:05:25 UTC
Created attachment 1453660 [details]
screenshot of throughput panel without units

Adding missing information, assuming the bug was found on sandbox-usm1 cluster,
with the following WA 3.4 packages:

[root@sandbox-usm1-server ~]# rpm -qa | grep tendrl | sort
tendrl-ansible-1.6.3-4.el7rhgs.noarch
tendrl-api-1.6.3-3.el7rhgs.noarch
tendrl-api-httpd-1.6.3-3.el7rhgs.noarch
tendrl-commons-1.6.3-6.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-4.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-4.el7rhgs.noarch
tendrl-node-agent-1.6.3-6.el7rhgs.noarch
tendrl-notifier-1.6.3-3.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-3.el7rhgs.noarch

[root@sandbox-usm1-gl1 ~]# rpm -qa | grep tendrl | sort
tendrl-collectd-selinux-1.5.4-2.el7rhgs.noarch
tendrl-commons-1.6.3-6.el7rhgs.noarch
tendrl-gluster-integration-1.6.3-4.el7rhgs.noarch
tendrl-node-agent-1.6.3-6.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch

Comment 4 Martin Bukatovic 2018-06-22 07:08:52 UTC
Acking assuming information stated in comment 3 are accurate (if not, I will
retract the qe ack no matter in which state the BZ will be later).

Comment 7 Nishanth Thomas 2018-06-26 08:04:38 UTC
Fixed via https://github.com/Tendrl/monitoring-integration/pull/502

Comment 9 Daniel Horák 2018-07-20 08:16:30 UTC
Created attachment 1464876 [details]
Throughput graph with units

Comment 10 Daniel Horák 2018-07-20 08:21:34 UTC
Tested and Verified on:
  grafana-4.3.2-3.el7rhgs.x86_64
  tendrl-ansible-1.6.3-5.el7rhgs.noarch
  tendrl-api-1.6.3-4.el7rhgs.noarch
  tendrl-api-httpd-1.6.3-4.el7rhgs.noarch
  tendrl-commons-1.6.3-9.el7rhgs.noarch
  tendrl-grafana-plugins-1.6.3-7.el7rhgs.noarch
  tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
  tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch
  tendrl-node-agent-1.6.3-9.el7rhgs.noarch
  tendrl-notifier-1.6.3-4.el7rhgs.noarch
  tendrl-selinux-1.5.4-2.el7rhgs.noarch
  tendrl-ui-1.6.3-7.el7rhgs.noarch

Throughput graph on the Cluster dashboard shows correct units (same as throughput
graph on Host Dashboard).
See attachment 1464876 [details].

>> VERIFIED

Comment 12 errata-xmlrpc 2018-09-04 07:07:57 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/RHSA-2018:2616