I have been trying to remediate a trigger for disk space <90.
This isn't an issue on any of our Baremetal servers but VSI's have a dev/loop* filesystem that cause the trigger to go off constantly.
the current trigger expression is:
last(Template-OS-Linux-VPN/vfs.fs.size[/,pfree])<90
discovery uses the Linux by Zabbix agent and gets moved to the above template.
On the Linux by Zabbix Agent template I have added to the discovery rule for Mounted filesystem discover the following:
Filter: {#FSNAME} matches @File systems for discovery exclude
under admin -> general - regular expressions I have:
File systems for discovery exclude
expressions -
Results are FALSE ^(/loop)$
the filesystems in question are:
/dev/loop0 64M 64M 0 100% /snap/core20/2015
/dev/loop1 64M 64M 0 100% /snap/core20/2105
/dev/loop2 92M 92M 0 100% /snap/lxd/24061
/dev/loop4 41M 41M 0 100% /snap/snapd/20290
/dev/loop5 41M 41M 0 100% /snap/snapd/20671
I'm not sure if the expression should be on /snap or the loop?
This isn't an issue on any of our Baremetal servers but VSI's have a dev/loop* filesystem that cause the trigger to go off constantly.
the current trigger expression is:
last(Template-OS-Linux-VPN/vfs.fs.size[/,pfree])<90
discovery uses the Linux by Zabbix agent and gets moved to the above template.
On the Linux by Zabbix Agent template I have added to the discovery rule for Mounted filesystem discover the following:
Filter: {#FSNAME} matches @File systems for discovery exclude
under admin -> general - regular expressions I have:
File systems for discovery exclude
expressions -
Results are FALSE ^(/loop)$
the filesystems in question are:
/dev/loop0 64M 64M 0 100% /snap/core20/2015
/dev/loop1 64M 64M 0 100% /snap/core20/2105
/dev/loop2 92M 92M 0 100% /snap/lxd/24061
/dev/loop4 41M 41M 0 100% /snap/snapd/20290
/dev/loop5 41M 41M 0 100% /snap/snapd/20671
I'm not sure if the expression should be on /snap or the loop?
Comment