Filesystem discovering finding too many filesystems

[dthacker]

Our zabbix server is running on 2.4.7 We are getting errors from filesystems that are no actually a filesystem.

We are monitoring file name /sa which is an NFS mount. Yesterday we several alarms for disk space for volumes like this:

"Free disk space is less than 20% on volume /sa/.snapshot/daily/2016-01-26_0010"

The /sa/.snapshot directory stores NetApp snapshots. We are using the mounted filesystem discover rule from the the Template OS Linux. The NFS is mounted on many (>20) servers, but only this server found this "extra" volumes.

1) What caused Zabbix to detect this other volumes?
2) How can I remove the items and triggers that were generated, the delete box in the item and triggers screen are not active. I am running with Super_Admin privileges.

I've attached a picture of the incorrect volume alarms.

TIA
Dave

[Atsushi]

If you're are using a Zabbix 2.4.7, I think that multiple filtering is usefull in the process of discovery.

https://www.zabbix.com/documentation/2.4/manual/discovery/low_level_discovery#discovery_of_file_systems

When you open "Mounted filesystem discovery" rule and select filter tab, you can see filtering rules.

By default, it is set only for file system type({#FSTYPE}).
Here, you will add a condition of the mount point({#FSNAME}).

Please refer to this post.

https://www.zabbix.com/forum/showthread.php?t=48529