Zabbix Documentation 3.2

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:concepts:definitions

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
manual:concepts:definitions [2017/08/24 19:29]
martins-v removing auto numbering
manual:concepts:definitions [2018/06/27 07:18] (current)
martins-v adding - event tags; event correlation, encryption
Line 1: Line 1:
-==== 1 Zabbix definitions ​====+====== 2. Definitions ======
  
 === Overview === === Overview ===
Line 21: Line 21:
 //​**[[manual:​config:​triggers|trigger]]**//​ //​**[[manual:​config:​triggers|trigger]]**//​
  
-- //a logical expression that defines a problem threshold and is used to "​evaluate"​ data received in items//+- //a logical expression that defines a problem threshold and is used to "​evaluate"​ data received in items.//
  
 When received data are above the threshold, triggers go from '​Ok'​ into a '​Problem'​ state. When received data are below the threshold, triggers stay in/return to an '​Ok'​ state. When received data are above the threshold, triggers go from '​Ok'​ into a '​Problem'​ state. When received data are below the threshold, triggers stay in/return to an '​Ok'​ state.
Line 27: Line 27:
 //​**[[manual:​config:​events|event]]**//​ //​**[[manual:​config:​events|event]]**//​
  
-- //a single occurrence of something that deserves attention such as a trigger changing state or a discovery/​agent auto-registration taking place//+- //a single occurrence of something that deserves attention such as a trigger changing state or a discovery/​agent auto-registration taking place.// 
 + 
 +//​**[[:​manual/​config/​triggers/​event_tags|event tag]]**// 
 + 
 +- //a pre-defined marker for the event.// It may be used in event correlation,​ permission granulation,​ etc. 
 + 
 +//​**[[:​manual/​config/​event_correlation|event correlation]]**//​ 
 + 
 +- //a method of correlating problems to their resolution flexibly and precisely.//​ 
 + 
 +For example, you may define that a problem reported by one trigger may be resolved by another trigger, which may even use a different data collection method.
  
 //​**[[manual:​web_interface:​frontend_sections:​monitoring:​problems|problem]]**//​ //​**[[manual:​web_interface:​frontend_sections:​monitoring:​problems|problem]]**//​
  
-- //a trigger that is in "​Problem"​ state//+- //a trigger that is in "​Problem"​ state.//
  
 //​**[[manual:​config:​notifications:​action|action]]**//​ //​**[[manual:​config:​notifications:​action|action]]**//​
Line 41: Line 51:
 //​**[[manual:​config:​notifications:​action:​escalations|escalation]]**//​ //​**[[manual:​config:​notifications:​action:​escalations|escalation]]**//​
  
-- //a custom scenario for executing operations within an action; a sequence of sending notifications/​executing remote commands//+- //a custom scenario for executing operations within an action; a sequence of sending notifications/​executing remote commands.//
  
 //​**[[manual:​config:​notifications:​media|media]]**//​ //​**[[manual:​config:​notifications:​media|media]]**//​
  
-- //a means of delivering notifications;​ delivery channel//+- //a means of delivering notifications;​ delivery channel.//
  
 //​**[[manual:​config:​notifications:​action:​operation:​message|notification]]**//​ //​**[[manual:​config:​notifications:​action:​operation:​message|notification]]**//​
  
-- //a message about some event sent to a user via the chosen media channel//+- //a message about some event sent to a user via the chosen media channel.//
  
 //​**[[manual:​config:​notifications:​action:​operation:​remote_command|remote command]]**//​ //​**[[manual:​config:​notifications:​action:​operation:​remote_command|remote command]]**//​
  
-- //a pre-defined command that is automatically executed on a monitored host upon some condition//+- //a pre-defined command that is automatically executed on a monitored host upon some condition.//
  
 //​**[[manual:​config:​templates|template]]**//​ //​**[[manual:​config:​templates|template]]**//​
  
-- //a set of entities (items, triggers, graphs, screens, applications,​ low-level discovery rules, web scenarios) ready to be applied to one or several hosts//+- //a set of entities (items, triggers, graphs, screens, applications,​ low-level discovery rules, web scenarios) ready to be applied to one or several hosts.//
  
 The job of templates is to speed up the deployment of monitoring tasks on a host; also to make it easier to apply mass changes to monitoring tasks. Templates are linked directly to individual hosts. The job of templates is to speed up the deployment of monitoring tasks on a host; also to make it easier to apply mass changes to monitoring tasks. Templates are linked directly to individual hosts.
Line 63: Line 73:
 //​**[[manual:​config:​items:​applications|application]]**//​ //​**[[manual:​config:​items:​applications|application]]**//​
  
-- //a grouping of items in a logical group//+- //a grouping of items in a logical group.//
  
 //​**[[manual:​web_monitoring|web scenario]]**//​ //​**[[manual:​web_monitoring|web scenario]]**//​
  
-- //one or several HTTP requests to check the availability of a web site//+- //one or several HTTP requests to check the availability of a web site.//
  
 //​**[[manual:​introduction:​overview#​architecture|frontend]]**//​ //​**[[manual:​introduction:​overview#​architecture|frontend]]**//​
  
-- //the web interface provided with Zabbix//+- //the web interface provided with Zabbix.//
  
 //​**[[manual:​api|Zabbix API]]**// //​**[[manual:​api|Zabbix API]]**//
  
-- //Zabbix API allows you to use the JSON RPC protocol to create, update and fetch Zabbix objects (like hosts, items, graphs and others) or perform any other custom tasks//+- //Zabbix API allows you to use the JSON RPC protocol to create, update and fetch Zabbix objects (like hosts, items, graphs and others) or perform any other custom tasks.// 
 + 
 +//​**[[manual:​concepts:​server|Zabbix server]]**//​ 
 + 
 +- //a central process of Zabbix software that performs monitoring, ​ interacts with Zabbix proxies and agents, calculates triggers, sends notifications;​ a central repository of data.//
  
-//**[[server|Zabbix ​server]]**//+//**[[manual:​concepts:​agent|Zabbix ​agent]]**//
  
-- //a central ​process ​of Zabbix software that performs ​monitoring,  interacts with Zabbix proxies ​and agents, calculates triggers, sends notifications;​ a central repository of data//+- //a process ​deployed on monitoring ​targets to actively monitor local resources ​and applications.//
  
-//**[[agent|Zabbix ​agent]]**//+//**[[manual:​concepts:​proxy|Zabbix ​proxy]]**//
  
-- //a process ​deployed ​on monitoring targets to actively monitor local resources and applications//+- //a process ​that may collect data on behalf of Zabbix server, taking some processing load off of the server.//
  
-//**[[proxy|Zabbix proxy]]**//+//**[[:​manual/​encryption|encryption]]**//
  
-- //a process that may collect data on behalf ​of Zabbix server, ​taking some processing load off of the server//+- //support ​of encrypted communications between ​Zabbix ​components (server, ​proxy, agent, zabbix_sender and zabbix_get utilities)// using Transport Layer Security (TLS) protocol.