14. Distributed monitoring [Zabbix]
Contents
1. Zabbix Manual Zabbix 11 21 13 4 25 PM Zabbix Manual Welcome to the user manual for Zabbix 2 0 software These pages are created to help our users successfully manage their monitoring tasks with Zabbix from the simple to the more complex 2 0 manual txt Last modified 2012 05 23 11 27 by martins v Except where otherwise noted content on this wiki is licensed under the following license CC Attribution Noncommercial Share Alike 3 0 Unported http creativecommons org licenses by nc sa 3 0 https www zabbix com documentation 2 0 manual Page 1 of 1 14 Distributed monitoring Zabbix 12 5 13 1 35 PM 14 Distributed monitoring Overview Zabbix provides effective and reliable ways of monitoring distributed IT infrastructure The two main solutions for large environments provided by Zabbix are use of proxies use of nodes Proxies can be used to collect data locally on behalf of a centralized Zabbix server and then report the data to the server Nodes are full Zabbix servers that can be set up in a hierarchy of distributed monitoring Proxy vs node When making a choice between using a proxy or a node several considerations must be taken into account es pop 1 Automatic DB creation feature only works with SQLite Other databases require a manual setup 2 0 manual distributed_monitoring txt Last modified 2011 12 27 17 55 by martins v Except where otherwise noted content on this wiki is licensed under the foll2. age 2 of 3 1 Proxies Zabbix 12 5 13 1 35 PM Parameter Description Enter the proxy name It must be the same name as in the Hostname parameter in the proxy configuration file Select the proxy mode Proxy mode Active the proxy will connect to the Zabbix server and request configuration data Passive Zabbix server connects to the proxy Add hosts to be monitored by the proxy Host configuration You can specify that an individual host should be monitored by a proxy in the host configuration form using the Monitored by proxy field Monitored by proxy no proxy Status Netherlands 2 0 manual distributed_monitoring proxies txt Last modified 2012 09 28 11 48 by martins v Except where otherwise noted content on this wiki is licensed under the following license CC Attribution Noncommercial Share Alike 3 0 Unported http creativecommons org licenses by nc sa 3 0 https www zabbix com documentation 2 0 manual distributed_monitoring proxies Page 3 of 3 2 Nodes Zabbix 12 5 13 1 36 PM 2 Nodes Overview You can use nodes to build a hierarchy of distributed monitoring Each node is a full Zabbix server and is responsible for monitoring its own location Zabbix supports up to a thousand nodes in a distributed setup The benefits of using a node setup building a multi level hierarchy of monitoring in a large network involving several geographical locations A node in the hierarchy reports to its m
3. aster node only anode can be configured locally or through its master node which has a copy of configuration data of all child nodes data gathering becomes more immune to possible communication problems If communication between a master and a child node breaks down nodes can keep operating Historical information and events are stored locally When communication is back a child node will optionally send the data to the master node the nodes can split the work of a single Zabbix server having to monitor thousands of hosts attaching and detaching new nodes does not affect the functionality of the existing setup No restart of any node required Platform independence A node may use its own platform OS hardware and database engine independently of other nodes Also child nodes can be installed without Zabbix frontend The nodes of higher levels should use a combination of better hardware with MySQL InnoDB Oracle or PostgreSQL backend A distributed monitoring setup will not work with an SQLite backend database Configuration Node configuration A Zabbix server installed by following the standard installation procedure is not configured as a node for a distributed setup To configure it as a node Specify a unique NodelD in the server configuration file zabbix_server conf Available values 1 999 O being the default value of a standalone server https www zabbix com documentation 2 0 manual distributed_monit
4. cense CC Attribution Noncommercial Share Alike 3 0 Unported http creativecommons org licenses by nc sa 3 0 https www zabbix com documentation 2 0 manual distributed_monitoring nodes Page 5 of 5
5. eBuffer parameters in the proxy configuration file control for how long the data are kept locally Zabbix proxy is a data collector It does not calculate triggers process events or send alerts For an overview of what proxy functionality is review the following table tems Zabbix agent checks Zabbix agent checks active https www zabbix com documentation 2 0 manual distributed_monitoring proxies Page 1 of 3 1 Proxies Zabbix Simple checks SNMP checks es es es es es es es ssns es o o es es es es No Built in web monitoring calculating triggers no Y Y Y Y Y Y Yes Yes Y Y Y Y 12 5 13 1 35 PM 1 To make sure that an agent asks the proxy and not the server for active checks the proxy must be listed in the ServerActive parameter in the agent configuration file Configuration Once you have installed and configured a proxy it is time to configure it in the Zabbix frontend Adding proxies To configure a proxy in Zabbix front end Go to Administration gt DM Select Proxies from the dropdown in the upper right corner Click on Create proxy or on the name of an existing proxy ci ee https www zabbix com documentation 2 0 manual distributed_monitoring proxies Proxy name Proxy mode Acia Hosts Proxy hosts New host Save Clone Delete Other hosts Hacseine Swech 2750 SFP Piu Host wih Nolepad Per we 349008 Switch 72676 ZAaDOU Serve P
6. oring nodes Page 1of5 2 Nodes Zabbix 12 5 13 1 36 PM Stop zabbix_server make sure that is is NOT running Convert database data for a distributed setup by running ee ee eee Run this command only once Running it twice will corrupt the database so make sure that you run it with the correct node id For example you may run if NodelD is 1 cd bin l zabbix_server n 1 c usr local etc zabbix_server conf ke l Running zabbix_server with the n option does not start the server process In a very simple setup we may envisage this node with NodelD 1 as the master and go on to configure another Zabbix server as a child node using the same procedure only using a different node identifier say 2 With two nodes configured it is time to add them in the Zabbix front end in a very simple master child relationship Front end configuration master node To configure the master node open its Zabbix frontend Go to Administration gt DM Make sure that Nodes are selected in the dropdown to the right Click on Local node to review its parameters Name ID 1 Type Local P Port 10051 Save Cancel Node attributes Unique node ID This is the value of NodelD from the configuration file Local the local node IP address of the local node Zabbix trapper must be listening on this IP address Port number of the local node Zabbix trapper must be listening on this port number Defaul
7. owing license CC Attribution Noncommercial Share Alike 3 0 Unported http creativecommons org licenses by nc sa 3 0 https www zabbix com documentation 2 0 manual distributed_monitoring Page 1 of 1 1 Proxies Zabbix 12 5 13 1 35 PM 1 Proxies Overview A Zabbix proxy can collect performance and availability data on behalf of the Zabbix server This way a proxy can take on itself some of the load of collecting data and offload the Zabbix server Also using a proxy is the easiest way of implementing centralized and distributed monitoring when all agents and proxies report to one Zabbix server and all data is collected centrally A Zabbix proxy can be used to Monitor remote locations Monitor locations having unreliable communications Offload the Zabbix server when monitoring thousands of devices Simplify the maintenance of distributed monitoring Firewall ZABBIX SERVER Remote location is monitored by single ZABBIX Proxy The proxy requires only one TCP connection to the Zabbix server This way it is easier to get around a firewall as you only need to configure one firewall rule Zabbix proxy must use a separate database Pointing it to the Zabbix server database will break the configuration All data collected by the proxy is stored locally before transmitting it over to the server This way no data is lost due to any temporary communication problems with the server The ProxyLoca Buffer and ProxyOfflin
8. s the NodelID from the master node configuration file Select the second of the two available values Type Child a child node Master a master node IP address of the master node Zabbix trapper must be listening on this IP address on the master node Port number of the master node Zabbix trapper must be listening on this port number Default is 10051 Starting server daemons To finish configuring a simple distributed setup start the zabbix_server daemons beginning with the master node daemon Display As soon as nodes are defined a dropdown for selecting one or several nodes appears in the Zabbix front end Current node Select Nodes a Al E me Local node Search Once selected all information displayed in the front end will come from the selected node s More complex configurations You can use the principles outlined to build more complex multi level monitoring hierarchies In this example Riga Node 4 will collect events and history from all the child nodes I Rio de Janeiro London Berlin Node 5 Node 1 Node 2 a Stockholm Paris Node 6 Node 3 a a Vilnius Riga Node 7 Node 4 https www zabbix com documentation 2 0 manual distributed_monitoring nodes Page 4 of 5 2 Nodes Zabbix 12 5 13 1 36 PM 2 0 manual distributed_monitoring nodes txt Last modified 2012 07 10 11 11 by martins v Except where otherwise noted content on this wiki is licensed under the following li
9. t is 10051 Then add the child node https www zabbix com documentation 2 0 manual distributed_monitoring nodes Page 2 of 5 2 Nodes Zabbix 12 5 13 1 36 PM Click on New node in Administration gt DM Name Child node Type Chid Master node Local node IP 192 168 1 5 5 Port 10051 Save J cancel Node attributes Unique name of the child node Unique node ID This is the NodelD from the child node configuration file Select the first of the two available values Child a child node Master a master node Select the master node for this child node IP address of the child node Zabbix trapper must be listening on this IP address Port number of the child node Zabbix trapper must be listening on this port number Default is 10051 Front end configuration child node To configure the child node open its Zabbix frontend Go to Administration gt DM Make sure that Nodes are selected in the dropdown to the right Click on Local node to review its parameters see above for how to configure the local node Then add the master node a Click on New node in Administration gt DM Master node Type Master IP 192 168 1 1 Port 1005 Name Save J cancel Node attributes Name Unique name of the master node https www zabbix com documentation 2 0 manual distributed_monitoring nodes Page 3 of 5 2 Nodes Zabbix 12 5 13 1 36 PM Unique master node ID This i
Download Pdf Manuals
Related Search