"vfs.fs.discovery" already exists on "Template OS Linux by Zabbix agent"

[cvee.it]

I am trying to configure a Linux file system template which will discover NFS4 and CIFS mount points, and then run a script stored locally on the Linux OS .

I have this all completed without a problem, however, in my testing, I only had the module template with the filesystem discovery and my unique macros linked to my test Linux host, and not the entire Linux OS Template.

My conflict is that I am recycling the use of the vfs.fs.discovery agent discovery key. I can't link my template like the existing module templates because it conflicts with "Template Module Linux filesystems by Zabbix agent".... rightly so ....

So how do I get access or perform the exact same filesystem discovery rule to be used independently of how the 'out of the box' Linux OS template is using it in the "Template Module Linux filesystems by Zabbix agent" ??

[gofree]

you might want to check filters option in LLD ( eg exclude through it some specific FS, drives, etc from general template )

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

[cvee.it]

It’s not the filters at fault . The out of the box template is fine , and I’ve added to it , but I don’t need network shares being alerted on during discovery , hence the independent template .

i also tried adding to Zabbix user parameters Conf file , I was able to call the same vfs discovery with an alias but the return json needs prefix truncated and or regex to make it work . Still working through this . It’s not 100% identical to calling vfs.discivery via agent

[cvee.it]

Resolved own issue.

I used vfs.fs.get as my discovery item, differing and therefore not conflicting with vfs.fs.dsicovery . Only available from version 4.4.5
Updated my agent which was only on 4.4.4 , and bingo! same FS discovery with independent filters not conflicting.