Zabbix Common terms

The following items are transferred from other websites. The specific source link cannot be found ....
Zabbix Common Terms
Host (hosts): The network device to be monitored, which can be specified by IP or DNS name
host group (hostname): A logical container for hosts, which can contain hosts and templates, but hosts and templates within the same group cannot be linked to each other; Host groups are typically used when assigning monitoring permissions to a user or group of users
Item (Monitoring item): The data of a particular monitoring indicator, which is from the monitored object; item is the core of data collection for Zabbix, no item, no data; Each item has a "key" identifier relative to a monitoring object
trigger (Trigger): An expression that evaluates whether the data received within a particular item of a monitor object is within a reasonable range, that is, the threshold value, the received data is greater than the threshold, and the trigger state is converted from OK to problem, and when the amount of data is returned to a reasonable range again, Its status will be converted from problem back to OK
Event (events): A noteworthy event that occurs, such as a change in the state of a trigger, the automatic registration of a new agent or a re-launched agent, and so on
Action (action): Refers to a pre-defined processing method for a specific event, by including an action (such as sending a notification) and a condition (when the action is taken)
escalation (Alarm upgrade ) : Send an alert or execute a custom scheme for remote commands, such as sending an alert every 5min, sending 5 times, etc.
Media (Media): Means and channels for sending notifications, such as email, jabber, or SMS
notification (notice): Information about an event sent to the user via the selected media (flexible mail sender is customizable)
Remote Command: Predefined commands that can be executed automatically when the monitored host is under a certain condition
template (templates): Used to quickly define a set of preset entries for a monitored host, usually containing item, trigger, graph, screen, application, and low-level discovery rule; templates can be linked directly to a single host
Application (Application): A collection of a set of item
Web Scennaro (web scene): One or more HTTP requests to detect Web site availability
frontend (front end): Zabbix's web interface

Zabbix Introduction Process composition

Zabbix_agentd
The client daemon, which collects client data, such as CPU load, memory, hard disk usage, etc.

zabbix_get
zabbix tool, which is used separately, usually executes commands to obtain remote client information on the server or proxy side. Usually the user is wrongly discharged. Example

zabbix_sender
zabbix tool, used to send data to a server or proxy, is typically used for lengthy checks. Many checks are time consuming, resulting in
zabbix timed out. So we use sender to commit the data after the script has finished executing.

zabbix_server
zabbix Server daemon. Zabbix_agentd, Zabbix_get, Zabbix_sender, Zabbix_proxy, Zabbix_java_gateway

Note: Of course, it is not the data are actively submitted to zabbix_server, there are some servers actively to fetch data.

< Span style= "FONT-SIZE:10PT;" > zabbix_ Proxy
zabbix Agent daemon. function is similar to server, the only difference is that it is just a broker, it needs to submit the collected data/be submitted to to In the server. Why use a proxy? What does an agent do? To sell a Xiaoguanzi, please continue to focus on Operation Survival time Zabbix Tutorial series.

< Span style= "FONT-SIZE:10PT;" > zabbix_java_gateway
zabbix2.0.

< Span style= "FONT-SIZE:10PT;" > Yes, it can only take the initiative to get the data, not passively fetch it. Its data will eventually be given to the server or proxy.

< Span style= "FONT-SIZE:10PT;" > < Span style= "FONT-SIZE:10PT;" > various processes introduced to this introduction, to Zabbix more, learn this chapter is particularly important.

Introduction to the Zabbix configuration Process
Zabbix configuration content More, we want to be divided into 9 chunks to explain. The following are the differences:
1. Host and Group
    Without the majority, as the name implies, he is adding host configuration with group configuration.
2. Monitoring items
    Items that need to be monitored, such as server load, can make a monitoring entry. The system comes with most of the monitoring items, some specific monitoring items we can customize
The method of customizing monitoring items is also discussed in the section "Zabbix Monitoring Items".
3. Trigger
    What happens when you start something, call it a trigger. For example: If the system load is greater than 10 then the alarm, this thing can be called the trigger .
4. Events
    Trigger state change, Discovery event, etc.
5. Visual Configuration
    Chart configuration, the monitoring of the data plotted as a graph. Or you can see all the monitoring charts of a host on a single screen.
6. Template Configuration
    < Span style= "FONT-SIZE:10PT;" > Custom monitoring templates. For example, Template os  Linux
7, Alarm configuration
Configure the alarm media: Mailbox, SMS, and when to send alert notifications.
user-defined variables, a useful feature.

This article is from the "Village Boys" blog, please make sure to keep this source http://noodle.blog.51cto.com/2925423/1768401

Zabbix Common terms