Description of problem: Status Information of Disk Utilization should show the actual disk usage status as well Version-Release number of selected component (if applicable): gluster-nagios-1.1-1.noarch.rpm gluster-nrpe-1.1-1.x86_64.rpm How reproducible: 100% Steps to Reproduce: 1.Add few RHS nodes and see the Disk Utilization in the Status Information 2. 3. Actual results: It lists only the disk names as given below ---- OK : disks:mounts:(/dev/sda1=/boot,/dev/mapper/vg_rhsclient16-lv_root=/,/dev/mapper/vg_rhsclient16-lv_home=/home) ---- Expected results: It should also show the current disk utilization of the disks listed similar to the ones seen under CPU, Memory and Swap Utilization status Additional info:
As discussed on 29-May-2014 : Though most of the team felt it's not a blocker, PM had input that considering it's related to storage, he would like to make it a blocker. Had it been for some other entity like CPU or memory, it would not have been a blocker. Marked blocker.
Disk utilization percentage is already available in the performance data and we have recently sent a patch to added an associated unit to the value. Adding anything more into status would cause increasing the status message length when the disk count is increasing in a node. Whereas same is not a case with cpu and memory.
Whenever a disk or inode reaches the threshold we are showing the fs, path and the usage% also. @Prasanth can you copy here the latest status output of disk usage
Currently it does not show the usage% only for the disks status "OK" Whenever a disk/inode reaches the threshold, it will immediately changes the status into "WARNING or CRITICAL" and will show the usage % also in the status message itself.
patch sent to upstream for review: http://review.gluster.org/#/c/7936/
use of -i option in the plugin -i MOUNTPATH, --include=MOUNTPATH ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Using this option one can add any disk (which is not listed for any reason) along with an existing list. Suppose if the disk is added twice/thrice/anytime unknowingly (due to huge list) the plugin will simply omits duplications.
(In reply to Timothy Asir from comment #8) > use of -i option in the plugin > > -i MOUNTPATH, --include=MOUNTPATH > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Using this option one can add any disk (which is not listed for any reason) > along with an existing list. Suppose if the disk is added > twice/thrice/anytime > unknowingly (due to huge list) the plugin will simply omits duplications. We can update the config file /etc/nagios/nrpe.cfg to use this option to include any extra disk to be monitored under section: "### START - configuration section for gluster nrpe plugins ###"
However, following is what I'm seeing in the "Status Information" of "Disk Utilization" on trying to verify this bug: ---- WARNING : 19.2% used (19.0GB out of 99.0GB) CRITICAL : 20.2% used (20.0GB out of 99.0GB) ---- As you can see, I'm NOT seeing the "disks:mounts" along with the WARNING and CRITICAL state of disk-utilization as mentioned by Dusmant on the closire of this bug. Is that a miss or am I missing something here? Please clarify. I'll attach the screenshots for the same. Moving this bug back to Assigned as it failed to verify.
Removing the blocker flag from this, after talking to PMs and Eric. We need to document this. Target it for 3.0.1 release.
(In reply to Prasanth from comment #11) > However, following is what I'm seeing in the "Status Information" of "Disk > Utilization" on trying to verify this bug: > > ---- > WARNING : 19.2% used (19.0GB out of 99.0GB) > > CRITICAL : 20.2% used (20.0GB out of 99.0GB) > ---- > > As you can see, I'm NOT seeing the "disks:mounts" along with the WARNING and > CRITICAL state of disk-utilization as mentioned by Dusmant on the closire of > this bug. Is that a miss or am I missing something here? Please clarify. > > I'll attach the screenshots for the same. > > Moving this bug back to Assigned as it failed to verify. It is there in Status Information only but it will be displayed only in the (detail view) Service state information page. We have added this feature to provide single line details as a short summery.
Hi, I noticed that the disk utilization performance data showed two sets of figures for each disk - /boot=8.00%;80;90;0;1.0 /boot=1.00%;80;90;0;128016.0 /=15.00%;80;90;0;18.0 /=4.00%;80;90;0;1148304.0 /rhs/brick1=40.00%;80;90;0;50.0 /rhs/brick1=1.00%;80;90;0;26212352.0 /rhs/brick2=40.00%;80;90;0;50.0 /rhs/brick2=1.00%;80;90;0;26212352.0 /rhs/brick3=1.00%;80;90;0;50.0 /rhs/brick3=1.00%;80;90;0;26212352.0 /rhs/brick4=91.00%;80;90;0;50.0 /rhs/brick4=1.00%;80;90;0;10179536.0 /rhs/brick5=1.00%;80;90;0;50.0 /rhs/brick5=1.00%;80;90;0;26212352.0 /rhs/brick6=1.00%;80;90;0;50.0 /rhs/brick6=1.00%;80;90;0;26212352.0 /rhs/brick7=1.00%;80;90;0;50.0 /rhs/brick7=1.00%;80;90;0;26212352.0 /rhs/brick8=1.00%;80;90;0;50.0 /rhs/brick8=1.00%;80;90;0;26212352.0 Also see screenshot attached. Is this behavior expected?
Created attachment 917698 [details] screenshot
yes one is for disk and another one is for inode.
Hi, I think it should be documented what each set of information denotes, as it is not clear by looking at the UI.
Its already documented in rhsc admin guide and rhs admin guide in "Using Nagios GUI" section.
Thank you for the bug report. However, closing this as the bug is filed against gluster nagios monitoring for which no further new development is being undertaken.