While many configuration parameters for a proxy are the same as for the server (the pollers to start, port to listen on, and so on), and some are the same as for the agent daemon (hostname), there are some proxy-specific parameters. Knowing about these can be helpful when diagnosing a proxy-related problem, or when the proxy must be deployed in a specific environment. For an active proxy, the following parameters affect it:
|
Option |
Description |
|
ProxyLocalBuffer |
Proxy will keep data in the local database for this many hours. By default, all data that is synchronized to the Zabbix server is removed. This could be useful if we would like to extract some data that is not stored permanently on the Zabbix server, such as network-discovery values. |
|
ProxyOfflineBuffer |
Proxy will keep data for this many hours if the Zabbix server is unavailable. By default, data older than one hour is discarded. |
|
HeartbeatFrequency |
By default, the Zabbix proxy sends a heartbeat message to the Zabbix server every minute. This parameter allows us to customize that. |
|
ConfigFrequency |
By default, the Zabbix proxy retrieves a new configuration from the server once per hour. You might want to increase this for large, fairly static setups, or maybe decrease it for smaller, more dynamic installations. Configuration data-retrieval can be forced by reloading the active proxy's configuration cache. |
|
DataSenderFrequency |
This parameter specifies how often the proxy pushes collected data to the Zabbix server. By default, it's one second. As all the trigger and alert processing is done by the server, it is suggested to keep this value low. If there are no values to send, an active proxy will not connect to the server except for heartbeat connections. |
For a passive proxy, ProxyMode allows us to switch to the passive mode. Now the communication is controlled by parameters in the server configuration file:
|
Option |
Description |
|
StartProxyPollers |
The number of processes that will be started and will connect to passive proxies to send configuration data and poll collected values. By default, one such process is started, and more might be needed if there are several passive proxies. |
|
ProxyConfigFrequency |
By default, Zabbix servers send configuration data to passive proxies once per hour. There is no way to force the sending of configuration data to passive proxies. This parameter affects connections to all passive proxies. |
|
ProxyDataFrequency |
This parameter specifies how often the proxy pushes collected data to the Zabbix server. By default, it's one second. The Zabbix server will connect to passive proxies even if they have no values to provide. This parameter affects connections to all passive proxies. |