Problems with Low Level Discovery and item prototypes

[torms]

Hi guys,

I have a problem with the LLD in Zabbix version 3.4. The standard Zabbix vfs.fs.discovery does not support mountpoint drives in windows. (only drives with letters are discoverd)
I have a windows powershell script that delivers a json response for discovery of mounted drives. This works ok.
See the JSON data at the bottom of the post.

I have created the following discovery rule:

https://ibb.co/moZeMR

Then I have created the following item prototypes:

https://ibb.co/gvam1R

With one drive everything works fine. The four items are successfully created.
But with more drives I get the following erros:

https://ibb.co/dzeDgR

I have used the LLD macro {#FSNAME} in the key name and think that the key names should be different if the macros are expanded.
Any suggestions to fix this?

Cu
Thomas



Compressed JSON Data:

{"data":[[{"{#FSNAME}":"C:\\Harddisks\\DBData\\AC\\","{#FSLA BEL}":"ACDATA","{#FSTYPE}":"NTFS"},{"{#FSNAME}":"C :\\Harddisks\\DBData\\EC\\","{#FSLABEL}":"ECDATA", "{#FSTYPE}":"NTFS"},{"{#FSNAME}":"C:\\Harddisks\\D BData\\EG\\","{#FSLABEL}":"EGDATA","{#FSTYPE}":"NT FS"},{"{#FSNAME}":"C:\\Harddisks\\DBData\\GR\\","{ #FSLABEL}":"GRDATA","{#FSTYPE}":"NTFS"},{"{#FSNAME }":"C:\\Harddisks\\DBData\\HB\\","{#FSLABEL}":"HBD ATA","{#FSTYPE}":"NTFS"},{"{#FSNAME}":"C:\\Harddis ks\\DBData\\MI\\","{#FSLABEL}":"MIDATA","{#FSTYPE} ":"NTFS"},{"{#FSNAME}":"C:\\Harddisks\\DBData\\NO\ \","{#FSLABEL}":"NODATA","{#FSTYPE}":"NTFS"},{"{#F SNAME}":"C:\\Harddisks\\DBData\\PE\\","{#FSLABEL}" :"PEDATA","{#FSTYPE}":"NTFS"},{"{#FSNAME}":"C:\\Ha rddisks\\DBData\\WS\\","{#FSLABEL}":"WSDATA","{#FS TYPE}":"NTFS"},{"{#FSNAME}":"C:\\Harddisks\\DBTemp Data\\","{#FSLABEL}":"DBTEMPDATA","{#FSTYPE}":"NTF S"},{"{#FSNAME}":"C:\\Harddisks\\DBTransLog\\","{# FSLABEL}":"DBTLOG","{#FSTYPE}":"NTFS"},{"{#FSNAME} ":"C:\\Harddisks\\DBData\\UN\\","{#FSLABEL}":"UNDA TA","{#FSTYPE}":"NTFS"},{"{#FSNAME}":"C:\\Harddisk s\\DBData\\HO\\","{#FSLABEL}":"HODATA","{#FSTYPE}" :"NTFS"},{"{#FSNAME}":"C:\\Harddisks\\DBData\\FR\\ ","{#FSLABEL}":"FRDATA","{#FSTYPE}":"NTFS"},{"{#FS NAME}":"C:\\","{#FSLABEL}":"System","{#FSTYPE}":"N TFS"}]]}


Formatted JSON Data:
{
"data":[
[
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\AC\\",
"{#FSLABEL}":"ACDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\EC\\",
"{#FSLABEL}":"ECDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\EG\\",
"{#FSLABEL}":"EGDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\GR\\",
"{#FSLABEL}":"GRDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\HB\\",
"{#FSLABEL}":"HBDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\MI\\",
"{#FSLABEL}":"MIDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\NO\\",
"{#FSLABEL}":"NODATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\PE\\",
"{#FSLABEL}":"PEDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\WS\\",
"{#FSLABEL}":"WSDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBTempData\\",
"{#FSLABEL}":"DBTEMPDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBTransLog\\",
"{#FSLABEL}":"DBTLOG",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\UN\\",
"{#FSLABEL}":"UNDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\HO\\",
"{#FSLABEL}":"HODATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\Harddisks\\DBData\\FR\\",
"{#FSLABEL}":"FRDATA",
"{#FSTYPE}":"NTFS"
},
{
"{#FSNAME}":"C:\\",
"{#FSLABEL}":"System",
"{#FSTYPE}":"NTFS"
}
]
]
}

[allexpetrov]

Hi,

you don't need to create the item prototype with this sytemrun. The item prototype is for Items only.

Your command should be in discovery rule, but in Item prototype you need to configure the metrics you want to receive from discovered hard drives.

Regards,
Alex!

[torms]

Hi Alex,

thanks for your reply. Nice hint that vfs.fs.size can handle mountpoints.

But the problem of the same key name was confusing.
Today I saw that there a two pairs of [[ ]] in the JSON.
So the JSON could be validated by a JSON validator but Zabbix seems to have a problem with it.

So i removed the duplicated [] and everything works like a charm.

Cu
Thomas