Table of Contents
2 Definitions
Overview
In this section you can learn the meaning of some terms commonly used in Áú»¢¶Ä²©.
Definitions
- any physical or virtual device, application, service, or any other logically-related collection of monitored parameters.
- a logical grouping of hosts; it may contain hosts and templates. Hosts and templates within a host group are not in any way linked to each other. Host groups are used when assigning access rights to hosts for different user groups.
- a particular piece of data that you want to receive from a host, a metric of data.
- a transformation of received metric value before saving it to the database.
- 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.
- a single occurrence of something that deserves attention such as a trigger changing state or a discovery/agent autoregistration taking place.
- a pre-defined marker for the event. It may be used in event correlation, permission granulation, etc.
- 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.
- a trigger that is in "Problem" state.
- problem management options provided by Áú»¢¶Ä²©, such as adding comment, acknowledging, changing severity or closing manually.
- a predefined means of reacting to an event.
An action consists of operations (e.g. sending a notification) and conditions (when the operation is carried out)
- a custom scenario for executing operations within an action; a sequence of sending notifications/executing remote commands.
- a means of delivering notifications; delivery channel.
- a message about some event sent to a user via the chosen media channel.
- a pre-defined command that is automatically executed on a monitored host upon some condition.
- a set of entities (items, triggers, graphs, 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.
- one or several HTTP requests to check the availability of a web site.
- the web interface provided with Áú»¢¶Ä²©.
- customizable section of the web interface displaying summaries and visualizations of important information in visual units called widgets.
- visual unit displaying information of a certain kind and source (a summary, a map, a graph, the clock, etc.), used in the dashboard.
- Áú»¢¶Ä²© API allows you to use the JSON RPC protocol to create, update and fetch Áú»¢¶Ä²© objects (like hosts, items, graphs and others) or perform any other custom tasks.
- a central process of Áú»¢¶Ä²© software that performs monitoring, interacts with Áú»¢¶Ä²© proxies and agents, calculates triggers, sends notifications; a central repository of data.
- a process that may collect data on behalf of Áú»¢¶Ä²© server, taking some processing load from the server.
- a process deployed on monitoring targets to actively monitor local resources and applications.
- a new generation of Áú»¢¶Ä²© agent to actively monitor local resources and applications, allowing to use custom plugins for monitoring.
Because Áú»¢¶Ä²© agent 2 shares much functionality with Áú»¢¶Ä²© agent, the term "Áú»¢¶Ä²© agent" in documentation stands for both - Áú»¢¶Ä²© agent and Áú»¢¶Ä²© agent 2, if the functional behavior is the same. Áú»¢¶Ä²© agent 2 is only specifically named where its functionality differs.
- support of encrypted communications between Áú»¢¶Ä²© components (server, proxy, agent, zabbix_sender and zabbix_get utilities) using Transport Layer Security (TLS) protocol.
- automated discovery of network devices.
- automated discovery of low-level entities on a particular device (e.g. file systems, network interfaces, etc).
- set of definitions for automated discovery of low-level entities on a device.
- 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.
- 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 Áú»¢¶Ä²© entities are also in use in low-level discovery - graph prototypes, host prototypes, host group prototypes.
- automated process whereby a Áú»¢¶Ä²© agent itself is registered as a host and started to monitor.