Description of problem ====================== Description of Throughput panel on Brick dashboard (Disk Load section) states that the values are fetched using `gluster volume profile` command, but the values are shown no matter if the gluster profiling is actually enabled. 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, disable profiling 3. Go to Brick dashboard and check description of "Througput" panel there (available via little "i" icon on top left corner of the panel). Actual results ============== The description states that the profiling information are used: > The Throughput panel displays brick-level read and write operations > fetched using “gluster volume profile”. But the data are shown anyway. See screenshot 1. Expected results ================ One of: * clarification what this panel actually reports in the description * fixing the way this panel fetches data (make it use profiling if that is actual intention) - based on information provided under bz 1590693, this seems not to be the case
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)