Replacement for Host Macros in LLD Prototype Names
We have recently upgraded from 5.X to 6.0, and have been bitten by the removal of the previously deprecated User Macros in LLD item/trigger names.
We create user macros with context for each disk so the teams receiving the alerts can receive meaningful data (ie "F:\ [Profile Data]", rather than just "F:"). To achieve this, there is a host macro {$DISK_NAME:"C:\ "}, set to "[Profile Data]". This host macro is then used in the item/trigger names by using {$DISK_NAME:"{#FSNAME} "} - which is obviously not longer expanded in 6+ of Zabbix. We use the same concept to override the trigger values - this still works, it's just the use of them in the name that's been ripped out.
I have found that where the Zabbix Agent is used, we can use {#FSLABEL}, which brings through the drive name in Windows (not ideal, but we can make it work). Unfortunately the VMware disk LLD doesn't have any other keys provided other than {#FSNAME}.
Has anyone else run into these challenges and found a way around them?
We create user macros with context for each disk so the teams receiving the alerts can receive meaningful data (ie "F:\ [Profile Data]", rather than just "F:"). To achieve this, there is a host macro {$DISK_NAME:"C:\ "}, set to "[Profile Data]". This host macro is then used in the item/trigger names by using {$DISK_NAME:"{#FSNAME} "} - which is obviously not longer expanded in 6+ of Zabbix. We use the same concept to override the trigger values - this still works, it's just the use of them in the name that's been ripped out.
I have found that where the Zabbix Agent is used, we can use {#FSLABEL}, which brings through the drive name in Windows (not ideal, but we can make it work). Unfortunately the VMware disk LLD doesn't have any other keys provided other than {#FSNAME}.
Has anyone else run into these challenges and found a way around them?