Ad Widget

Collapse

File discovery not showing all filesystems on one Windows server

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • poldermonitor
    Junior Member
    • Jun 2026
    • 1

    #1

    File discovery not showing all filesystems on one Windows server

    Hello,

    I actually already asked this on Reddit, but only just noticed there’s a dedicated Zabbix community here as well so reposting my question here.

    I'm running into a strange issue with file discovery on one of my Windows servers and was hoping someone here might have seen this before.

    The server has 43 disks, and all of them are detected correctly via disk discovery. However, with filesystem discovery (vfs.fs.discovery), only 11 filesystems are being discovered, while I expect around 46.
    The odd part is that when I run the command locally on the server:

    zabbix_agent2.exe -t vfs.fs.discovery

    it correctly returns all filesystems.
    Even more confusing: in Zabbix, I do see some of the expected entries, for example:

    {"{#FSNAME}":"D:\\Clinical\\departmenta","{#FST YPE }":"NTFS","{#FSLABEL}":"[Clinical] - departmenta","{#FSDRIVETYPE}":"fixed"}

    But very similar ones are missing, like this one:

    {"{#FSNAME}":"D:\\Clinical\\departmentb","{#FST YPE }":"NTFS","{#FSLABEL}":"[Clinical] - departmentb","{#FSDRIVETYPE}":"fixed"}

    (The names are slightly modified to avoid sharing company data.)

    So it seems the agent can discover them, but for some reason Zabbix only processes or shows a subset.

    Does anyone have an idea why one filesystem would be included while another nearly identical one is not? Could this be related to LLD filters, limits, or something else I'm overlooking?

    Does anyone know how I can make sure all filesystems are discovered?
Working...