Zabbix Documentation 5.0

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 [2019/10/07 06:35]
127.0.0.1 external edit
manual:introduction:overview [2020/05/20 03:54] (current)
marinagen [Agent] mentioning agent 2
Line 23: Line 23:
 == Agent == == 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. +Zabbix agents are deployed on monitoring targets to actively monitor local resources and applications and report the gathered data to Zabbix server. ​Since Zabbix 4.4, there are two types of agents available: the [[manual:​concepts:​agent|Zabbix agent]] (lightweight,​ supported on many platforms, written in C) and the [[manual:​concepts:​agent|Zabbix agent 2]] (extra-flexible,​ easily extendable with plugins, written in Go). 
 === Data flow === === 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. 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.