Low Level discovery and cdrom

[HeadQuaker]

Hello,

I have set a LLD for hard drive.
It is working, a bit too much because i can see cdrom/dvdrom too;

How can I avoid this ?
Useing Filter ? What should i set?

thank you

SOLVED : the issue was just the delay of applying the template modification to all hosts... So dumb

[HeadQuaker]

Hi,
Already seen that but it does not working, probably i'm doing it bad.
It is in windows environment

[HeadQuaker]

Any idea ?

What i have set :

{#FSDRIVETYPE} not match cdrom

[Hamardaban]

Show which key you use for LLD and which json it returns for some host with a cdrom.

[HeadQuaker]

My LLD is like that :
Zabbix Agent, key : vfs.fs.discovery

How can i see the json ?
zabbix get agent ?

Thx for ur help

[Hamardaban]

At zabbix server- zabbix_get -s IP_OF_HOST -k "vfs.fs.discovery"

[HeadQuaker]

it seems good :

[{"{#FSNAME}":"C:","{#FSTYPE}":"NTFS","{#FSDRIVE TYP E}":"fixed"},{"{#FSNAME}":"D:","{#FSTYPE}":"UDF" ," {#FSDRIVETYPE}":"cdrom"}]

but not working... hum

[Hamardaban]

That's all right. Show how the filter is configured (picture)?

[HeadQuaker]

It seems working now... Maybe it was the delay of applying the modification on template to hosts.
Thanks for your help, I've learn how to see json from servers

[Hamardaban]

That's good! For information, there is a timeout for the zabbix server to apply the saved configuration.

[HeadQuaker]

Yes but it takes a really long time the check is every 1H, that's why i found it strange.

[cyber]

Filtering is described in

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

Even examples are for filesystem discovery.