- 1 Active
- 2 Active checker
- 3 Action
- 4 Agent
- 5 Alerter
- 6 Auto-registration
- 7 Auto-discovery
- 8 Event
- 9 Graphs
- 10 Host
- 11 Housekeeper
- 12 IT Services
- 13 Item
- 14 Location
- 15 Map
- 16 Master or Master Node
- 17 Media Type
- 18 Node
- 19 Node ID
- 20 Node Watcher
- 21 Queue
- 22 Passive
- 23 Poller
- 24 ROI
- 25 Screen
- 26 Sender
- 27 Server
- 28 SLA
- 29 Slave or Slave Node
- 30 Template
- 31 Timer
- 32 Trapper
- 33 Trigger
- 34 User
- 35 User parameter
- 36 ZABBIX
- 37 ZABBIX SIA
Active refers to a mode that the ZABBIX Agent can run in. When running actively, the agent keeps track of what items to send to the server and at what intervals. The agent can poll the server at set intervals in order to keep track of what items it should be sending.
Active checker gather operational information from the system where ZABBIX Agent is running, and report this data to the ZABBIX for further processing.
An action is a response taken when a Trigger has been triggered. Actions can be configured to send messages to specific user groups as defined in ZABBIX, based on their Media Type settings, or execute remote commands.
Agent refers to the program that is run on hosts that want to be monitored. It is run as a service and can process both active and passive checks simultaneously.
Alerter is a server process which is responsible for execution of actions (emails, jabber, SMS, scripts).
Auto-registration refers to a feature of ZABBIX that allows Hosts to automatically register themselves with the ZABBIX server. This is configured via the web interface by an administrator that defines a particular Hostname patter such as ‘*-Linux’ and define Items for that host based on a Template of items.
ZABBIX auto-discovery module is a module which performs automated discovery of hosts and services and generating events for further processing.
An event is when a trigger is triggered.
Graphs can refer to the simple graphs that are available for each numerical Item that is monitored, or it can refer to custom graphs which can be used to show several numerical Items in one graph.
Host refers to the machine that is being monitored.
Housekeeper refers to the service within the ZABBIX server that cleans the ZABBIX database of old actions, events, history, and trend data as defined by the user. Housekeeping of Actions and Events is defined in General settings. History and trend data is defined per item.
IT Services refers to a feature within ZABBIX that allows users to define an SLA and have ZABBIX keep track of the expected SLA and actual SLA. IT Services are defined as groups of triggers and can be configured to calculate the minimum of a group or maximum of a group.
Item refers to an individual item that is monitored on a host, such as load average or response time. Item can refer to an item obtained via the ZABBIX agent, SNMP, or other means. Items can be configured as float, 64-bit integers, character strings, or log values.
Environment monitored by a single Node.
Map refers to a feature of ZABBIX that allows users to create customized graphics via the web interface to create network maps and define links between Hosts on the map. Links can be configured to change color or style based on Triggers.
Master or Master Node
Master Node. Master Node may have one or several Slaves.Master Node can control configuration of the Slaves.
Media Types are used to notify ZABBIX users when an Action has occurred. Media types can be via email or custom scripts. Media Types are configured globally to be made available to all Users, and then specified per User to allow certain Users to be notified via one media type, and other users to be notified via another media type.
ZABBIX Server in distributed setup monitoring number of hosts.
Node ID is a unique number which identifies Node. Each Node must have its own unique Node ID.
ZABBIX Server process which takes care of inter-node communications.
Queue refers to the internal queue of items the ZABBIX server is monitoring. Based on the specified intervals of items the ZABBIX server maintains a queue to keep track of the items and when it should poll them.
Passive refers to a mode that the ZABBIX Agent can run in. When running passively, the agent waits for requests for items from the server and sends them back as requested. It should be noted that typically the agent runs in both modes, and the modes are defined by the Item when it is configured.
I can't believe I've been going for years without kwonnig that.
ZABBIX Server process which is responsible for retrieval of data from ZABBIX and SNMP agents and processing remote (simple) checks.
Return on Investment.
Screen refers to another customizable feature of ZABBIX which allows users to create custom pages within ZABBIX for displaying information. A screen can consist of graphs (custom), simple graphs, maps, or plain text such as the last 5 values of a particular item.
ZABBIX utility which sends data to ZABBIX Server for further processing. It usually used in user scripts.
Server refers to the program that is run on a centralized machine that has been deemed the “monitoring station”. The server is run as a service and is in charge of keeping track of all the configured hosts, items, actions, alerts, etc.
SLA refers to Service Level Agreement. These are typically used in contracts between companies and clients in order to define a certain level of service such as 99.5% availability of a particular Host.
Slave or Slave Node
Slave Node is linked to a Master Node. Slave Nodes reports to Master Node.
A Template is a Host that has a defined set of Items, Triggers, etc. which Hosts can be linked to. This allows easier configuration of hosts and changes to hosts without having to change each individual host. Host Templates are no different from other hosts except that their status is set to ‘Template’ during configuration and as such no Host is actually monitored.
ZABBIX Server process responsible for processing of date and time related functions of trigger expressions.
ZABBIX Server process responsible for processing of ZABBIX Agent (active) checks, log files and data sent by sender.
A trigger is used to define constraints on items and provide notifications when these constraints are exceeded. For example, you could be monitoring load average on a specific host and want to know when load average exceeds 1.0. Triggers are very flexible and can allow for multiple constraints.
The ZABBIX web front-end can be configured to allow access to multiple users at varying levels of access. Users can be allowed anonymous access via the guest account and be allowed to view all available data but not modify any changes, or users can be given access to only view or modify specific sections of ZABBIX.
User Parameter (UserParameter) refers to custom scripts defined in an agent’s configuration file. User parameters are defined by a key and command. The key refers to the item defined in the web interface and can be configured to accept arguments as sent by the server.
Latvian company that develops and provides support for ZABBIX.