Bug 1613729 - There are 2 similar charts for brick utilization on Brick dashboard
Summary: There are 2 similar charts for brick utilization on Brick 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: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.4.z Batch Update 1
Assignee: gowtham
QA Contact: Elena Bondarenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-08 08:51 UTC by Martin Bukatovic
Modified: 2018-10-31 08:45 UTC (History)
11 users (show)

Fixed In Version: tendrl-monitoring-integration-1.6.3-13.el7rhgs
Doc Type: Bug Fix
Doc Text:
Previously, there were two panels, Capacity Utilization and Mount Point Utilization in the Brick dashboard that displayed the same metric for brick utilization. Having two different panels displaying the same data was confusing. Therefore, to avoid any confusion, the Mount Point Utilization panel is now discarded and the Capacity Utilization panel is retained to display brick utilization metrics.
Clone Of:
Environment:
Last Closed: 2018-10-31 08:45:18 UTC
Embargoed:


Attachments (Terms of Use)
screenshot 1: two utilization charts on brick dashboard (246.13 KB, image/png)
2018-08-08 08:54 UTC, Martin Bukatovic
no flags Details
node2_Brick3 (181.35 KB, image/png)
2018-09-06 08:51 UTC, gowtham
no flags Details
node2_brick4 (177.38 KB, image/png)
2018-09-06 08:52 UTC, gowtham
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github Tendrl monitoring-integration issues 549 0 None None None 2018-09-07 08:19:17 UTC
Red Hat Product Errata RHBA-2018:3427 0 None None None 2018-10-31 08:45:44 UTC

Description Martin Bukatovic 2018-08-08 08:51:35 UTC
Description of problem
======================

There are 2 similar charts for brick utilization on Brick dashboard:

 * Mount Point Utilization chart in Disk Load section
 * Capacity Utilization in At-a-Glance section

Both seems to display the same data, but the description doesn't explain
why do we have both and where is the difference.

Version-Release number of selected component
============================================

tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch

How reproducible
================

100 %

Steps to Reproduce
==================

1. Instal RHGS WA using tendrl-ansible
2. Import Trusted storage pool with at least one volume, enable profiling
3. Run some workload for few hours
4. Check Brick dashboard

Actual results
==============

There are 2 similar charts for brick utilization on Brick dashboard, reporting
the same data, but it's not clear what is the difference between the two.

Description of Capacity Utilization chart:

> The Capacity Utilization panel displays the brick capacity utilization
> over a period of time.

Description of Mount Point Utilization chart:

> The Mount Point Utilization for a given brick over a period of time.

See screenshot 1.

Expected results
================

It's clear why do we have 2 utilization charts in brick dashboard, and what
is the difference between them. We may need ot 

Or if there is no reason for this, there is only single utilization chart on
the brick dashboard.

Comment 1 Martin Bukatovic 2018-08-08 08:54:01 UTC
Created attachment 1474199 [details]
screenshot 1: two utilization charts on brick dashboard

Comment 3 gowtham 2018-09-06 08:50:42 UTC
I have created two brick in a same device "vdd". 

vdd                                 252:48   0   20G  0 disk 
├─mygroup-mythinpool1_tmeta         253:12   0    8M  0 lvm
│ └─mygroup-mythinpool1-tpool       253:14   0    8G  0 lvm
│   ├─mygroup-mythinpool1           253:18   0    8G  0 lvm
│   └─mygroup-thinv1                253:19   0    1G  0 lvm  /gluster/brick3
├─mygroup-mythinpool1_tdata         253:13   0    8G  0 lvm
│ └─mygroup-mythinpool1-tpool       253:14   0    8G  0 lvm
│   ├─mygroup-mythinpool1           253:18   0    8G  0 lvm
│   └─mygroup-thinv1                253:19   0    1G  0 lvm  /gluster/brick3
├─mygroup-mythinpool2_tmeta         253:15   0    8M  0 lvm
│ └─mygroup-mythinpool2-tpool       253:17   0    8G  0 lvm
│   ├─mygroup-mythinpool2           253:20   0    8G  0 lvm
│   └─mygroup-thinv2                253:21   0    1G  0 lvm  /gluster/brick4
└─mygroup-mythinpool2_tdata         253:16   0    8G  0 lvm
  └─mygroup-mythinpool2-tpool       253:17   0    8G  0 lvm
    ├─mygroup-mythinpool2           253:20   0    8G  0 lvm
    └─mygroup-thinv2                253:21   0    1G  0 lvm  /gluster/brick4

and i have created volume using these two bricks, i have filled up "/gluster/brick3" with some data. In grafana for only utilization value is raised for "/gluster/brick3" and mountpoint panel and capacity utilization panel shows same value for "/gluster/brick3".

no utilization change in "/gluster/brick4" dashbaord.


Which means both capacity utilization and mount_point utilization calculated using brick_mount point only.


i have seen code for mountpoint utilization and capacity utilization both are calculated using brick mount point only.

These two are actually redundant, I feel we can remove mounpoint panel

Comment 4 gowtham 2018-09-06 08:51:53 UTC
Created attachment 1481228 [details]
node2_Brick3

Comment 5 gowtham 2018-09-06 08:52:25 UTC
Created attachment 1481229 [details]
node2_brick4

Comment 6 Martin Bukatovic 2018-09-06 11:55:50 UTC
(In reply to gowtham from comment #3)
> These two are actually redundant, I feel we can remove mounpoint panel

Thank you for the evaluation. Based on your results, I agree with removal of
"Mount Point Utilization" chart in "Disk Load" section.

Comment 7 gowtham 2018-09-07 08:19:17 UTC
PR is under review: https://github.com/Tendrl/monitoring-integration/pull/550

Comment 10 Elena Bondarenko 2018-09-25 11:43:16 UTC
There is only Capacity Utilization chart now, no Mount Point Utilization chart.

Comment 16 Anmol Sachan 2018-10-23 09:38:28 UTC
Looks good.

Comment 18 errata-xmlrpc 2018-10-31 08:45:18 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-2018:3427


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