While proxies have many benefits, they do have some limitations, too. Well, pretty much one main limitation—they are only data collectors. If the server cannot be reached, the proxy cannot do independent notifications. They can't even generate events; all logic regarding triggers is processed on the server only. Remember, proxies do not process events, send out alerts, or execute remote commands. Remote commands, discussed in Chapter 7, Acting upon Monitored Conditions, are currently scheduled for Zabbix 3.2—but one would have to see that version released to be sure about such a feature being implemented.
Let's talk about how proxies operate a bit. We'll cover three things here:
Synchronization of the configuration
Synchronization of the collected data
Operation during maintenance
By default, proxies synchronize the configuration once per hour, and this period can be set in the zabbix_proxy.conf
configuration file. Look for the parameter named ConfigFrequency
...