If you're not opposed to another dependency, there is a glusterfs-nagios package (python-based) which presents the volumes in a much more useful format for monitoring.
http://download.gluster.org/pub/gluster/glusterfs-nagios/1.1.0/ Patrick On Tue, Jun 21, 2016 at 10:28 AM, Malte Schmidt <[email protected]> wrote: > Under which conditions does "gluster volume status $volume detail" return > something else than a table? > > Typical, expected output: > > root@server1:~# gluster volume status vol0 detail > Status of volume: vol0 > > ------------------------------------------------------------------------------ > Brick : Brick server1:/data/glusterfs/vol0 > TCP Port : 49152 > RDMA Port : 0 > Online : Y > Pid : 2942 > File System : xfs > Device : /dev/mapper/glusterfs > Mount Options : rw,relatime,attr2,inode64,noquota > Inode Size : 512 > Disk Space Free : 9.0GB > Total Disk Space : 20.0GB > Inode Count : 10485760 > Free Inodes : 8774085 > > ------------------------------------------------------------------------------ > Brick : Brick server2:/data/glusterfs/vol0 > TCP Port : 49152 > RDMA Port : 0 > Online : Y > Pid : 3275 > File System : xfs > Device : /dev/mapper/glusterfs > Mount Options : rw,relatime,attr2,inode64,noquota > Inode Size : 512 > Disk Space Free : 9.0GB > Total Disk Space : 20.0GB > Inode Count : 10485760 > Free Inodes : 8774085 > > Are there any conditions under which that table is different? Better > question: What is the best way of getting this data for usage in Nagios? > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
