In Zabbix 6.0, I am using the "VMWARE" template with a discovery rule that has an associated host prototype used to create Zabbix hosts for discovered VMs. The "VMWARE" template assigns the "VMWARE Guest" template to the discovered VM hosts.
We have several VMWARE clusters for different clients, and when an alert related to a discovered VM arrives, we would like to easily distinguish in the alert message which client the host belongs to.
I thought of this possibility:
1. In the host linked to the "VMWARE" template (VMWARE cluster node) from which the VMs are discovered, set a macro {$NAME} that represents the name of the client to whom that VMWARE cluster belongs.
2. Within the host prototype, add the {$NAME} macro (along with {#VM.NAME}) in the Visible name, so that the Zabbix hosts of the discovered VMs have something in common with the VMWARE cluster host in their name
I tested it and it doesn't seem to work: although the discovered VM hosts inherit the {$NAME} macro (and its value) from the VMWARE cluster node, it does not appear in the visible name of VMs.
I searched on internet and it seems that this feature (macro in host prototype name) is not actually implemented.
Is there anyone who has the same need (distinguishing from which VMWARE node the alerts come) and has found an effective way to solve the problem?
We have several VMWARE clusters for different clients, and when an alert related to a discovered VM arrives, we would like to easily distinguish in the alert message which client the host belongs to.
I thought of this possibility:
1. In the host linked to the "VMWARE" template (VMWARE cluster node) from which the VMs are discovered, set a macro {$NAME} that represents the name of the client to whom that VMWARE cluster belongs.
2. Within the host prototype, add the {$NAME} macro (along with {#VM.NAME}) in the Visible name, so that the Zabbix hosts of the discovered VMs have something in common with the VMWARE cluster host in their name
I tested it and it doesn't seem to work: although the discovered VM hosts inherit the {$NAME} macro (and its value) from the VMWARE cluster node, it does not appear in the visible name of VMs.
I searched on internet and it seems that this feature (macro in host prototype name) is not actually implemented.
Is there anyone who has the same need (distinguishing from which VMWARE node the alerts come) and has found an effective way to solve the problem?