Auto registration vs. Discovery actions

[horkyze]

I am trying to set up automatic discovery with via proxy. After setting up a Discovery action with following operations:

Add host
Add to host groups: some_group
Add to host groups: Discovered hosts
Link to templates: awesome_tamplate
Enable host

restarting proxy, wait for received configuration data from server at "x.x.x.x", datalen 24457 message , but host are not shown, not even after few mins.

But create Auto registration action with the same operations, and host are added.

My question here is what is the difference between Auto registration and Discovery actions and why isn't the Discovery action sufficient.

[kloczek]

Autodiscovery and autoregistrations are not the alternatives.
Usually autoregistration is used with active agents and autodiscovery with passive one.
In other words those two techniques are used in different situations.

[horkyze]

Thanks for quick reply.
Can you provide more detail?
I assumed that the Discovery action will be triggered when the Discovery Conditions are met, but it looks like that Discovery action is not triggered.

[Atsushi]

In Auto registration, when the Zabbix server is connected from the Zabbix agent, it processes the connection source host.
In Discovery, the Zabbix server polls each IP address within the range of the IP address set in the discovery rule, checks it, and processes the host with the IP address that responded.

In discovery, events are processed only at the timing of polling on the Zabbix server side. Discovery event actions are not executed when connected from the Zabbix agent.
If the IP range of the discovery rule is wide, be aware that it takes time to check all the IP addresses in the range.