Bug 1613533
| Summary: | Description of Throughput panel on Brick dashboard states it depends on gluster profiling, but it shown data with disabled profiling anyway | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Martin Bukatovic <mbukatov> | ||||
| Component: | web-admin-tendrl-monitoring-integration | Assignee: | gowtham <gshanmug> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | sds-qe-bugs | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rhgs-3.4 | CC: | mbukatov, nthomas, rhs-bugs, sankarshan, shtripat | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-05-08 16:11:43 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-07 18:52:34 UTC
Created attachment 1474078 [details]
screenshot 1: Throughput panel on Brick dashboard with disabled profiling
What option proposed in Expected results section is expected? Martin all details under disk_load in brick dashboards are fetched using psutil library, not from volume profiling command. It is not related to volume profile enable. all disk details are collected using mount point. gowtham answered the question from comment 2, thank you Martin, based on https://bugzilla.redhat.com/show_bug.cgi?id=1613533#c4 is this still a valid issue? (In reply to Shubhendu Tripathi from comment #6) > Martin, based on https://bugzilla.redhat.com/show_bug.cgi?id=1613533#c4 is > this still a valid issue? I don't see any reason for this issue to be invalid. The description is wrong, we are fetching this information using device names of the brick from the output of psutil.disk_io_counters(perdisk=True) |