Zabbix Documentation 4.0

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:definitions

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:definitions [2018/06/27 06:49]
martins-v adding - preprocessing; event tags; event correlation
manual:definitions [2019/05/16 13:24] (current)
martins-v fixing link target
Line 21: Line 21:
 //​**[[:​manual/​config/​items/​item#​item_value_preprocessing|value preprocessing]]**//​ //​**[[:​manual/​config/​items/​item#​item_value_preprocessing|value preprocessing]]**//​
  
-- //a transformation of received metric value// before saving ​them to the database+- //a transformation of received metric value// before saving ​it to the database.
  
 //​**[[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 31: Line 31:
 //​**[[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]]**//+//​**[[:​manual/​config/​event_correlation/​trigger/​event_tags|event tag]]**//
  
-- //a pre-defined marker for the event//It may be used in event correlation,​ permission granulation,​ etc.+- //a pre-defined marker for the event.// It may be used in event correlation,​ permission granulation,​ etc.
  
 //​**[[:​manual/​config/​event_correlation|event correlation]]**//​ //​**[[:​manual/​config/​event_correlation|event correlation]]**//​
  
-- //a method of correlating problems to their resolution flexibly and precisely//.+- //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. 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.
Line 45: Line 45:
 //​**[[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/​acknowledges#​updating_problems|problem update]]**//​ 
 + 
 +- //problem management options provided by Zabbix, such as adding comment, acknowledging,​ changing severity or closing manually.//
  
 //​**[[manual:​config:​notifications:​action|action]]**//​ //​**[[manual:​config:​notifications:​action|action]]**//​
Line 55: Line 59:
 //​**[[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 77: Line 81:
 //​**[[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/​web_interface/​frontend_sections/​monitoring/​dashboard|dashboard]]**//​ 
 + 
 +- //​customizable section of the web interface displaying summaries and visualisations//​ of important information in visual units called widgets. 
 + 
 +//​**[[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets|widget]]**//​ 
 + 
 +- //visual unit displaying information of a certain kind and source// (a summary, a map, a graph, the clock, etc), used in the dashboard.
  
 //​**[[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]]**//​ //​**[[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//+- //a central process of Zabbix software that performs monitoring, ​ interacts with Zabbix proxies and agents, calculates triggers, sends notifications;​ a central repository of data.//
  
 //​**[[manual:​concepts:​agent|Zabbix agent]]**// //​**[[manual:​concepts:​agent|Zabbix agent]]**//
  
-- //a process deployed on monitoring targets to actively monitor local resources and applications//​+- //a process deployed on monitoring targets to actively monitor local resources and applications.//
  
 //​**[[manual:​concepts:​proxy|Zabbix proxy]]**// //​**[[manual:​concepts:​proxy|Zabbix proxy]]**//
  
-- //a process that may collect data on behalf of Zabbix server, taking some processing load off of the server//+- //a process that may collect data on behalf of Zabbix server, taking some processing load off of the server.// 
 + 
 +//​**[[:​manual/​encryption|encryption]]**//​ 
 + 
 +- //support of encrypted communications between Zabbix components (server, proxy, agent, zabbix_sender and zabbix_get utilities)//​ using Transport Layer Security (TLS) protocol. 
 + 
 +//​**[[:​manual/​discovery/​network_discovery|network discovery]]**//​ 
 + 
 +- //automated discovery of network devices//​. 
 + 
 +//​**[[:​manual/​discovery/​low_level_discovery|low-level discovery]]**//​ 
 + 
 +- //automated discovery of low-level entities on a particular device// (e.g. file systems, network interfaces, etc). 
 + 
 +//​**[[:​manual/​discovery/​low_level_discovery#​discovery_rule|low-level discovery rule]]**//​ 
 + 
 +- //set of definitions for automated discovery of low-level entities// on a device. 
 + 
 +//​**[[:​manual/​discovery/​low_level_discovery#​item_prototypes|item prototype]]**//​ 
 + 
 +- //a metric with certain parameters as variables, ready for low-level discovery//​. After low-level discovery the variables are automatically substituted with the real discovered parameters and the metric automatically starts gathering data. 
 + 
 +//​**[[:​manual/​discovery/​low_level_discovery#​trigger_prototypes|trigger prototype]]**//​ 
 + 
 +- //a trigger with certain parameters as variables, ready for low-level discovery//​. After low-level discovery the variables are automatically substituted with the real discovered parameters and the trigger automatically starts evaluating data. 
 + 
 +//​Prototypes//​ of some other Zabbix entities are also in use in low-level discovery - graph prototypes, host prototypes, host group prototypes, application prototypes. 
 + 
 +//​**[[:​manual/​discovery/​auto_registration|agent auto-registration]]**//​ 
 + 
 +- //automated process whereby a Zabbix agent itself is registered//​ as a host and started to monitor.