Bug 1613729
| Summary: | There are 2 similar charts for brick utilization on Brick dashboard | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Martin Bukatovic <mbukatov> | ||||||||
| Component: | web-admin-tendrl-monitoring-integration | Assignee: | gowtham <gshanmug> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Elena Bondarenko <ebondare> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rhgs-3.4 | CC: | apaladug, asachan, asriram, ebondare, gshanmug, nthomas, rghatvis, rhinduja, rhs-bugs, sankarshan, shtripat | ||||||||
| Target Milestone: | --- | Keywords: | ZStream | ||||||||
| Target Release: | RHGS 3.4.z Batch Update 1 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| 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.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-10-31 08:45:18 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Martin Bukatovic
2018-08-08 08:51:35 UTC
Created attachment 1474199 [details]
screenshot 1: two utilization charts on brick dashboard
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
Created attachment 1481228 [details]
node2_Brick3
Created attachment 1481229 [details]
node2_brick4
(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. PR is under review: https://github.com/Tendrl/monitoring-integration/pull/550 There is only Capacity Utilization chart now, no Mount Point Utilization chart. Looks good. 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 |