Zabbix Documentation 4.2

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:introduction:overview

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:introduction:overview [2016/02/16 15:25]
manual:introduction:overview [2018/10/01 09:42] (current)
Line 1: Line 1:
 +==== 4 Zabbix overview ====
 +
 +=== Architecture ===
 +
 +Zabbix consists of several major software components, the responsibilities of which are outlined below.
 +
 +== Server ==
 +
 +[[manual:​concepts:​server|Zabbix server]] is the central component to which agents report availability and integrity information and statistics. The server is the central repository in which all configuration,​ statistical and operational data are stored.
 +
 +== Database storage ==
 +
 +All configuration information as well as the data gathered by Zabbix is stored in a database.
 +
 +== Web interface ==
 +
 +For an easy access to Zabbix from anywhere and from any platform, the web-based interface is provided. The interface is part of Zabbix server, and usually (but not necessarily) runs on the same physical machine as the one running the server.
 +
 +== Proxy ==
 +
 +[[manual:​concepts:​proxy|Zabbix proxy]] can collect performance and availability data on behalf of Zabbix server. A proxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server.
 +
 +== Agent ==
 +
 +[[manual:​concepts:​agent|Zabbix agents]] are deployed on monitoring targets to actively monitor local resources and applications and report the gathered data to Zabbix server.
 +
 +=== Data flow ===
 +
 +In addition it is important to take a step back and have a look at the overall data flow within Zabbix. ​ In order to create an item that gathers data you must first create a host. Moving to the other end of the Zabbix spectrum you must first have an item to create a trigger. ​ You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on //Server X// you must first create a host entry for //Server X// followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed by an action which sends you an email. While that may seem like a lot of steps, with the use of templating it really isn't. However, due to this design it is possible to create a very flexible setup.