This page provides details on the monitoring configuration update for the proxy, i.e. how changes made to the monitoring configuration on the server are synchronized to the proxy.
The proxy configuration update is incremental. During a configuration sync only those entities are updated that have been changed; if there has been no change, nothing is sent. This approach allows to save resources and set a smaller interval (almost instant) for the proxy configuration update.
Proxy configuration changes are tracked using revision numbers. Only entities with revisions larger than the proxy configuration revision are included in configuration data sent to the proxy.
The entities for a configuration sync are as follows:
|autoregistration tls data||All autoregistration TLS data.|
|expressions||All expressions (regular expressions, expression tables).|
|global configuration||Global configuration defined in the 'config' table|
|host||All properties, interfaces, inventory, items, item preprocessing, item parameters, web scenarios of a host.|
|host macros||All macros defined on a host and all template IDs linked to it.|
|proxy discovery rule||Discovery rules and checks assigned to a proxy.|
An exception are the host macros which are sent also if anything on the host has been changed.
-R config_cache_reload command on the proxy will also initiate an incremental update.
Note that a full configuration sync will take place on a proxy start/restart, HA failover, if the session token has changed, or if the configuration update failed on the proxy, for example, if the connection was broken while receiving configuration data.
The ProxyConfigFrequency parameter determines how often the proxy configuration is synced with the server (10 seconds by default).
Note that ProxyConfigFrequency is:
On active proxies ProxyConfigFrequency is a new parameter since Zabbix 6.4 and must be used instead of the now-deprecated ConfigFrequency.
If both ProxyConfigFrequency and ConfigFrequency are used, the proxy will log an error and terminate.