How does zabbix agent discover disks/interfaces?

[MustQ]

Hello,

In the built in templates for OS windows and OS linux, how does the agent find the desired information (like a new disk or a new network interface) and provide it to zabbix?

We're having a problem and trying to rule out zabbix from the mix. All our windows servers seemed to have a TON of background running processes with net.exe. I had scripts that would periodically mount/unmount a network drive to copy files and ensure zabbix is updated automagically. Everytime such a drive mount would occur, zabbix would pick up this drive as a new disk. We're worried that this might use the net.exe command and cause the issue we're having.

So this is more of a question of "how does the zabbix agent interact with windows to get discovery information" than anything.

Thank you!

[Atsushi]

Defalut Template is discovering each 1 hour(= 3600 sec).
If you added disk or network interface, Zabbix agent discover that items with each hour by discovery settings.

Please check discovery setting for "Template OS Linux" and "Template OS Windows".

If you don't want check temporary mount disk, you can filtering for target.
But, defining several filters is supported since Zabbix 2.4.

Low-level discovery:

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

[MustQ]

Thank you for your reply Atushi. I understand that I can filter things out by modifying the low level discovery rules, and how often zabbix checks for discovery.

My question is more about how the zabbix agent actually (programatically) finds this information. Is the agent using wmi to query the OS and then take the results and feed them to zabbix in a "zabbix friendly format"? We are trying to determine if zabbix played a role in the heightened number of processes on our servers.