Zabbix Discovery Actions not evaluating correctly.
Dear team,
I've set up the network discovery with several rules in order to discover over my network checking many /28 IP ranges. Each /28 is getting the hosts for a different POP on my network. On the discovery rule I've set up the OID to get the Hostname and a string which contains the brand & model of the equipment that is being monitored. All my discovery rules are being discovered on 3 different Proxies.
I've set up also my Discovery actions separating the different brands using the predefined templates for Cisco, Juniper, Mikrotik and some own templates for other Brands. On my last Discovery Action I've created an Action that assigns a Generic templated for the hosts that don't belong to any of the other brands (please find attached a screenshot of the Discovery actions).
Unfortunately on my logs I'm receiving a message mentioning that some equipment cannot be linked to the Generic Template (the one that is not for a particular Brand) because of a conflicting item key "icmpping". The thing is that actually the host is already assigned to the correct Brand template because has been prevously assigned by the correct rule.
330934:20210430:165538.480 cannot link template(s) "Core - Device - Generic - SNMP" to host "Juniper-HOSTX": conflicting item key "icmpping" found
I'm assuming that my Zabbix is having some issue on evaluating the Condition on my Discovery Action.
We are running Zabbix 5.2.6 both on a lab environment (own Server) and production environment (AWS) and we are getting our logs full of these messages which I'd like to not receive any more.
Does anyone experienced the same issue? Is there any way to resolve this?
Thanks in advance.
I've set up the network discovery with several rules in order to discover over my network checking many /28 IP ranges. Each /28 is getting the hosts for a different POP on my network. On the discovery rule I've set up the OID to get the Hostname and a string which contains the brand & model of the equipment that is being monitored. All my discovery rules are being discovered on 3 different Proxies.
I've set up also my Discovery actions separating the different brands using the predefined templates for Cisco, Juniper, Mikrotik and some own templates for other Brands. On my last Discovery Action I've created an Action that assigns a Generic templated for the hosts that don't belong to any of the other brands (please find attached a screenshot of the Discovery actions).
Unfortunately on my logs I'm receiving a message mentioning that some equipment cannot be linked to the Generic Template (the one that is not for a particular Brand) because of a conflicting item key "icmpping". The thing is that actually the host is already assigned to the correct Brand template because has been prevously assigned by the correct rule.
330934:20210430:165538.480 cannot link template(s) "Core - Device - Generic - SNMP" to host "Juniper-HOSTX": conflicting item key "icmpping" found
I'm assuming that my Zabbix is having some issue on evaluating the Condition on my Discovery Action.
We are running Zabbix 5.2.6 both on a lab environment (own Server) and production environment (AWS) and we are getting our logs full of these messages which I'd like to not receive any more.
Does anyone experienced the same issue? Is there any way to resolve this?
Thanks in advance.
Attached Files
Comment