Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.
Deploying a proxy is optional, but may be very beneficial to distribute the load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry.
A Zabbix proxy is the ideal solution for centralized monitoring of remote locations, branches and networks with no local administrators.
Zabbix proxy requires a separate database.
Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations as, for example, in return values of low-level discovery rules.
Zabbix proxy runs as a daemon process. The proxy can be started by executing:
This will work on most of GNU/Linux systems. On other systems you may need to run:
Similarly, for stopping/restarting/viewing status of Zabbix proxy, use the following commands:
If the above does not work you have to start it manually. Find the path to the zabbix_proxy binary and execute:
You can use the following command line parameters with Zabbix proxy:
Runtime control is not supported on OpenBSD and NetBSD.
Examples of running Zabbix proxy with command line parameters:
Runtime control options:
|config_cache_reload||Reload configuration cache. Ignored if cache is being currently loaded.
Active Zabbix proxy will connect to the Zabbix server and request configuration data.
|housekeeper_execute||Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.|
|log_level_increase[=<target>]||Increase log level, affects all processes if target is not specified.||pid - Process identifier (1 to 65535)
process type - All processes of specified type (e.g., poller)
process type,N - Process type and number (e.g., poller,3)
|log_level_decrease[=<target>]||Decrease log level, affects all processes if target is not specified.|
Allowed range of PIDs for changing the log level of a single Zabbx process is from 1 to 65535. On systems with large PIDs <process type,N> target option can be used for changing the log level of a single process.
Example of using runtime control to reload the proxy configuration cache:
Example of using runtime control to trigger execution of housekeeper
Examples of using runtime control to change log level:
Increase log level of all processes: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase Increase log level of second poller process: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=poller,2 Increase log level of process with PID 1234: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=1234 Decrease log level of all http poller processes: shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_decrease="http poller"
Zabbix proxy is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run proxy as any non-root user without any issues.
If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run proxy as 'root' if you modify the 'AllowRoot' parameter in the proxy configuration file accordingly.
See the configuration file options for details on configuring zabbix_proxy.
Zabbix proxy runs on the same list of server#supported platforms as Zabbix server.
Note that the proxy requires a UTF-8 locale so that some textual items can be interpreted correctly. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically.