Windows 2012 R2 client with 64 Zabbix agent and SATA drives.

Oh, remark here.

I did not see any problems on my side with this. But I am not sure why. Maybe because amount of files dropped by 30% (but size increased). maybe, because I set Timeout option on zabbix agent to 15 seconds.

Timeout=15

Anyway if timeout option works - it should be documented in item description. Thanks.

Hi,

The vfs.dir.size relies on the same Timeout setting in zabbix_server.conf and zabbix_agentd.conf files as any other standard agent item. Getting the data for directory sizes takes the same amount of time as du -sb dir executed from the command line. The more directories have to be counted the more time it takes.

You may either limit the number of directories counted, limit the depth or increase the Timeout setting in the configuration files.

To see how much time does it actually take to return a value you may execute the following command from your Zabbix server's command line:

time zabbix_get -s <IP or DNS of the agent> -k vfs.dir.size[<directory>]

After seeing the results set the Timeout setting, restart the services and now you should be able to monitor directories as expected.

Apparently we were posting comments at the same time and you had already found the right solution.

The timeout applies to all agent items not only this one, but agreed that this item is likely more affected than others. Suggestion about the documentation noted.

The vfs.dir.size item is dependent on the timeout setting. There is nothing we can do to override this behavior as this applies to all Zabbix agent items.

Steps to troubleshoot have been provided. Additionally, notes on the documentation have been added under ZBX-12757.

Closing this issue as Won't fix.

Steps to reproduce:

1. i change Tmeout in zabbix_agentd.win.cong in zabbix client
2. i run zabbix_get -s ip -k vfs.dir.size[C:/Windows/]

Result:

Expected:

i want a to monitore size of this folder "c:/Windows"