Trigger of "mounted filesystem discovery" doesn't work

[FrM222]

Hello together,

I'm new in this forum and I am a beginner with Zabbix. So sorry in advanced, if I make any mistakes.

For our Servers we have configured the standard-template "Windows by Zabbix Agent". There is on the Discovery Rules also the "mounted filesystem discovery" includet. All drives on a server will be scanned on "total space", "used space" and "space utilization (in %)".


In principle, these queries also work, results are recorded.


On these Discovery-Rule are also Trigger configured. Here should be warned, if the space utilization is over 80% and give a critical notification if the space utilization is over 90%.



Now my problem is, that this trigger-warning doesn't work. How you can see in the picture above, the drive G has a space utilization of 88%. So I should get a warning, but according to Zabbix everything is fine on this server.

Has anyone an idea, why this trigger doesn't work and how I can get the warning?

Thank you very much in advanced for your help.

[cyber]

That condition has 2 parts (Description in trigger conf shows it), so if just one matches, then it will not fire... Just in case check, what's the values for {$VFS.FS.FREE.MIN.WARN:"{#FSNAME}"}. You seem to have big disks there, maybe that value is too small. The other part is fill rate, what we cannot calculate here anyway...

[cyber]

That condition has 2 parts (Description in trigger conf shows it), so if just one matches, then it will not fire... Just in case check, what's the values for {$VFS.FS.FREE.MIN.WARN:"{#FSNAME}"}. You seem to have big disks there, maybe that value is too small. The other part is fill rate, what we cannot calculate here anyway...

[FrM222]

Hello cyber,

yes, you are right. I haven't noticed that there is an additional part....
I deleted the additional part from the trigger, because we have big disks and if the space utilization is over 80%, the free space is not always under 10GB.
But now I have the problem, that this change does not work for the existing hosts.
Here I did the change:


And this is the item and trigger on the host configuration:


Do you have any idea how I can get the change on the existing hosts?

[cyber]

Discovery needs to run again. What's the interval there? You can probably force discovery on a host to see if something changes...

[FrM222]

Oh okay, I think I was too impatient. Now it works.