Zabbix is software that keeps track of numerous specifications of a network and the health and integrity of servers. Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send out the info to the Zabbix server, essentially working on behalf of the server. All collected data is buffered in your area and then moved to the Zabbix server the proxy belongs to. Deploying a proxy is optional, but may be extremely advantageous to distribute the load of a single Zabbix server. If only proxies gather data, processing on the server ends up being less CPU and disk I/O starving.
How Does the Proxy Work
Only the Zabbix proxy links to the Zabbix serverv. This little information is essential to comprehending how it actually works. When the proxy connects to the server, it demands setup info about exactly what it has to monitor, then goes and does simply that. As data is gathered, proxy sends it back to the server. Does that noise familiar? It should, because that part sounds just like an active agent, except that the proxy can gather data from various systems pretty much like the Zabbix server can. It sounds practically like an incredibly agent. Really, it is said that the proxy was at first internally named “extremely agent”, which verifies the resemblance.
The Zabbix proxy is a really useful feature, the very first steady Zabbix version to present it was 1.6, back in 2008. Given the effectiveness of the Zabbix proxy, it is surprising that for a very long time no other options offered something similar. Today, Zabbix proxies continue to blaze a trail by having and improving features that are thought about most helpful for remote information collection. As will see later, there are other advantages that proxies can provide, so let’s get to really setting one up, click here .
How independent is a proxy truly? What happens if the server goes down? We can find a configuration criterion called ProxyOfflineBuffer if we look at/ etc/zabbix/zabbix _ proxy.conf. This specification manages how long the proxy will keep data in it’s regional database (in hours) in case Zabbix server can not be contacted. Being one hour by default, this indicates the Zabbix server can be down or unreachable for approximately one hour, and we would not lose any information as long as it came back online prior to the hour was up. Of course, you can increase this period but make certain you have enough complimentary disk area, specifically if running on embedded hardware.
There’s one caution a proxy is a data collector only. This suggests that proxy does not procedure events, send informs, or perform remote commands. You need to pass the information to the Zabbix server so that it can do all those things. The s proxies can collect information while the Zabbix server is down or inaccessible for some reason and buffer this data for the configured period. Still lose one hour worth of data if the Zabbix server was down for two hours.