I feel I understand Zabbix on an active level and monitor hundreds of hosts using old manual methodologies, but not so much discover processes. I have a scenario where I have 2 discovery rules in place for a subnet.
Rule #1 checks 172.22.0.1-254, for Zabbix Agent on Port 10055 for agent.hostname. For Device uniqueness, Hostname, and Visible name, I have it set to utilize Zabbix Agent (10055) agent.hostname. The agent.hostnames for example are: abc254.domain.com
Rule #2 checks 172.22.0.1-254, for Zabbix Agent on Port 10056 for agent.hostname. For Device uniqueness, Hostname, and Visible name, I have it set to utilize Zabbix Agent (10056) agent.hostname. So they are almost the exact same with the exception of the passive port. The agent.hostnames for example are: abc254-service
Under monitoring and discovery it shows that the right hosts are discovered properly. I have two discovery actions in place:
Discovery action #1 - Check equals Zabbix Agent 10055 agent.hostname AND Discovery status equals Up, Service type equals Zabbix Agent, and Host IP equals 172.22.0.1-254. When found it adds to a specific host group and adds Templates (Lets just say SystemD and Linux by Zabbix Agent).
Discovery action #2 - Check equals Zabbix Agent 10056 agent.hostname AND Discovery status equals Up, Service type equals Zabbix Agent, and Host IP equals 172.22.0.1-254. When found it adds to a specific host group and adds templates (Lets just say "Container Agent" ).
When only Action Rule #1 or #2 is enabled it functions as necessary, and populates the correct Host Name, assigns the templates and Host Groups.
When both actions are enabled output is much different - The Hostname becomes the first Discovery Action found, and only one set of the discovery actions is applied in terms of templates, when looking at the host detail it shows two interfaces configured both to the same IP address with the two different ports. I am expecting that it would have created multiple hosts with their own unique hostnames and templates/groups and interfaces. Is this a bug?
Zabbix Server and agents (modern/2) 5.4.8. I am running multiple agents on the host, yet the 10056 port agent is a Docker container but using network: host which is sharing the same IP as the baremetal host.