Bug 1595013 - Provide the appropriate title for two IOPS panels in host dashboard
Summary: Provide the appropriate title for two IOPS panels in host dashboard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-monitoring-integration
Version: rhgs-3.4
Hardware: All
OS: All
urgent
high
Target Milestone: ---
: RHGS 3.4.0
Assignee: Ankush Behl
QA Contact: Martin Bukatovic
URL:
Whiteboard:
Depends On: 1593912
Blocks: 1503137
TreeView+ depends on / blocked
 
Reported: 2018-06-26 00:56 UTC by Anand Paladugu
Modified: 2021-09-09 14:44 UTC (History)
5 users (show)

Fixed In Version: tendrl-monitoring-integration-1.6.3-6.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 07:08:24 UTC
Embargoed:


Attachments (Terms of Use)
screenshot of IOPS charts on brick dashboard (200.67 KB, image/png)
2018-06-27 17:40 UTC, Martin Bukatovic
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2616 0 None None None 2018-09-04 07:09:30 UTC

Description Anand Paladugu 2018-06-26 00:56:34 UTC
Description of problem:  IOPS metric panels in Host dashboard are consistent amongst themselves and with the IOPS metric in Cluster dashboard.

Based on the discussion with Nishant it seemed like the IOPS metric panel is for the bricks (aggregate IOPS for bricks on that node) and Disk Operation is the Disk IOPS for that host.   If so we should appropriately change the headings (Brick IOPS and Disk IOPS), Update the panel information and also make the panels consistent with the one in Cluster view Dashboard.



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


How reproducible: Always


Steps to Reproduce:
1.  View and compare IOPS metrics in host dashboard (IOPS and Disk Operation)
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Martin Bukatovic 2018-06-27 17:29:53 UTC
Assuming this has been reported based on sandbox-usm1 instance, the
full package version list follows:

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

Comment 3 Martin Bukatovic 2018-06-27 17:36:53 UTC
Asking for clarification: In this BZ, you write about few problems:

1) IOPS metric panels in Host dashboard are consistent amongst themselves
   and with the IOPS metric in Cluster dashboard
2) labeling problem with IOPS metric panel is for the bricks (clarification
   request)

Is the 1st problem the same as described in BZ 1593912?

If yes, let's rescope this BZ to be concerned about problem #2 only and change
title accordingly.

Comment 4 Martin Bukatovic 2018-06-27 17:40:04 UTC
Created attachment 1455102 [details]
screenshot of IOPS charts on brick dashboard

Attaching screenshot of IOPS charts on brick dashboard.

Comment 5 Anand Paladugu 2018-07-03 12:45:28 UTC
Martin.   All IOPS panels should be consistent across all dashboards. They are not.  I think I missed the work "not" in the BZ title and problem description. 

Plus within the host dashboard we have two IOPS panels and looks like per Nishanth one is for Brick level and the other is for Disk level.  I am changing the title accordingly, but let us make sure that IOPS panels are consistent across.

Comment 6 Martin Bukatovic 2018-07-04 11:54:10 UTC
QE will verify that:

 * titles of IOPS charts are updated as stated in comment 5 and description
 * affected IOPS charts are consistent with all other IOPS charts in other
   dashboards

Also:

 * this BZ should be verified only after BZ 1593912 is fixed and verified to
   prevent moving this BZ to FailedQE state accidentally

Comment 10 Martin Bukatovic 2018-08-15 17:55:11 UTC
Comment on attachment 1455102 [details]
screenshot of IOPS charts on brick dashboard

The screenshot shows Brick dashboard, while this BZ is about Host and
Cluster dashboards only. There is a separate BZ for the issue demonstrated
on the screenshot: BZ 1613705

Comment 11 Martin Bukatovic 2018-08-15 18:09:05 UTC
Testing with
============

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

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

Results
=======

Titles of IOPS charts were updated as stated in comment 5 and description: now
there are Brick IOPS panel (At-a-Glance) and Disk IOPS panel (Capacity & Disk
Load) on Host dashboard.

Affected IOPS charts on Host dashboards are consistent with IOPS chart from
Cluster dashboard (based on visual inspection): appropriate description is
used, data are presented in expected way and peaks shown in IOPS charts
matches.

Note that there is a separate bug for issues with IOPS panels on Brick
dashboard: BZ 1613705

Comment 13 errata-xmlrpc 2018-09-04 07:08:24 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


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