Monitoring if a filesystem is no longer discovered by low level discovery

[eav]

Hi all,

I have a problem I'm not quite sure how to handle and was wondering if you could help.
The other day one of our windows fileservers had one of its volumes disconnected, and we had no idea until users started calling.

So I decided to add a trigger that would notify us if any filesystem was suddendly no longer discovered by low level discovery.
The trigger I came up with is this:

(({MyTemplate:vfs.fs.size[{#FSNAME},pused].nodata(5m)} = 1) and ({MyTemplate:agent.ping.nodata(5m)}=0))

The problem is, when a filesystem goes offline, all the items associated with it become unsupported, in this case MyTemplate:vfs.fs.size[{#FSNAME},pused].nodata(5m)} = 1), and the trigger doesn't fire.
The Zabbix version that we are using is 2.4.4

My question is, am I doing anything wrong or is this expected behaviour?
What is the point of the nodata() function then?
Is there any workaround?

Thank you in advance for the help

[inhayn]

Hello,

You can try this:

https://www.zabbix.com/documentation/2.4/manual/config/notifications/unsupported_item

[sugraj1119]

low level discovery issue with file system type filter

Dear Team, Kinldy help me to resolve low level discovery issue with file systems.
I have applied discovery for Solaris server which has 2.0.9 version by #FSTYPE filter but it didnt discover any file systems.
When i checked port 10050 is not enabled at host level but 10051 is enabled.

Whether discovery will depends on port 10050, if not how to resolve this issue.

Kindly assist