Duplicate Volumes (vfs.fs)

[HANDL_Eric]

We recently started getting alerts for a handful of Windows systems that are being monitored by the Zabbix agent for low disk space. At first glace, one of our admins jumped onto the endpoints when the alerts triggered and realized there was plenty of space left on the volume and closed the alerts. Well after this started becoming a reoccurring theme I started looking into it and realized that the alerts were triggering based on false items tied to the hosts in Zabbix.

From what I can see for the impacted systems, they all have duplicate items for the volumes in question including Total Space, Free Space, & space utilization. They have the same names and volume serial numbers listed between the pairs, but the larger of the two carries a higher key id. I'm really not sure where to start, but my first thought is knowing these are all virtual machines that the volumes in question were extended at some point and although unchanged outside of size, Zabbix is importing them as a new volume instead of updating the existing item.

Is this a known thing or maybe a setting we need to modify to prevent this from happening going forward?

[cyber]

I guess this is somekind of discovery and index of discovered items is changed, so what previously was #4, is now #5... New items/triggers are created. But maybe old ones are marked now as "not discovered any more" and you can just delete old ones. Maybe setting a "keep lost resources" period for shorter time might avoid such thing in the future...

[HANDL_Eric]

cyber the interesting part is that the storage metrics for the lower indexed item are still moving and triggering alerts which tells me Zabbix believes both items are alive.