Shulou(Shulou.com)06/02 Report--

Distributed system monitoring tool Zabbix how to use, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

For operation and maintenance personnel, monitoring is very important, because if we want to ensure the overall stable operation of online business, then we need to pay real-time attention to whether the indicators related to it are normal, and behind a business system, there are often a lot of servers, network equipment and other hardware resources, if we want to be able to more convenient and centralized monitoring of them. We need to rely on some external tools, and zabbix is a widely used application that enables centralized monitoring and management.

I. the characteristics of zabbix

Zabbix is an enterprise-level open source solution based on WEB interface that provides distributed system monitoring and network monitoring capabilities. Zabbix can monitor various network parameters to ensure the safe operation of the server system, and provides a flexible notification mechanism to enable system administrators to quickly locate / solve various problems. This is a definition of zabbix on Baidu Encyclopedia. There are many monitoring software on the market, so why choose zabbix? First, let's take a look at its characteristics:

1, automatically discover servers and network devices.

2. Automatic discovery of the underlying layer

3. Distributed monitoring system and centralized web management

4. Support active monitoring and passive monitoring mode

5. Supports multiple operating systems such as Linux, Solaris, HP-UX, AIX, FreeBSD, OpenBSD, OS X

6. Efficient agent supports Linux, Solaris, HP-UX, AIX, FreeBSD, OpenBSD,OS X, Tru64/OSF1, Windows NT4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista environments

7, no agent monitoring and other monitoring methods.

8. Secure user authentication mode

9, flexible user rights settings.

10, the management method based on web.

11, support free custom events and mail delivery.

12. High-level business view to monitor resources.

13. Support log audit.

II. Components and processes of zabbix

module

Zabbix consists of the following components:

1. Zabbix Server: the core component responsible for receiving the report information sent by agent. All configuration, statistics and operation data are organized by it.

2. Database Storage: dedicated to storing all configuration information and data collected by zabbix

3. GUI interface of Web interface:zabbix, which usually runs on the same host as Server.

4. Proxy: optional component, often used in distributed monitoring environment. The agent Server collects the monitoring data of the monitored side and sends it to the server side.

5. Agent: deployed on the monitored host, responsible for collecting local data and sending it to Server or proxy

Note: zabbix node is also a kind of zabbix server.

Process

By default, zabbix contains five programs: zabbix_agentd, zabbix_get, zabbix_proxy, zabbix_sender, and zabbix_server. Another zabbix_java_gateway is optional, which needs to be installed separately. Let's introduce their respective roles.

Zabbix_agentd client daemon, which collects client data, such as cpu load, memory, hard disk usage, and so on.

The zabbix_getzabbix tool, a command used alone, usually executes a command to get remote client information on the server or proxy side. Usually the user troubleshoots. For example, if the client's memory data cannot be obtained on the server side, we can use zabbix_get to obtain the client's content for troubleshooting.

The zabbix_senderzabbix tool, used to send data to server or proxy, is usually used for time-consuming checks. Many checks are time-consuming, causing zabbix to time out. So after the script has been executed, we use sender to actively submit the data. Zabbix_serverzabbix server daemon. The data of zabbix_agentd, zabbix_get, zabbix_sender, zabbix_proxy and zabbix_java_gateway are ultimately submitted to server comments: of course, not all data is actively submitted to zabbix_server, and some server takes the initiative to fetch data.

Zabbix_proxyzabbix proxy daemon. The function is similar to server, except that it is only a transit station, and it needs to submit / submit the collected data to server. Why use an agent? What does the agent do? As a matter of fact, please continue to follow the zabbix tutorial series of operation and maintenance survival time.

A feature introduced after zabbix_java_gatewayzabbix2.0. As the name implies: Java gateway, similar to agentd, but only for Java. Special attention should be paid to the fact that it can only obtain data actively, not passively. Its data will eventually be given to server or proxy.

The following figure is the logical diagram of zabbix:

Operation and maintenance Monitoring tool zabbix Overview of Operation and maintenance Monitoring tool zabbix III. Related terms in zabbix monitoring environment

1. Host (host): the network device to be monitored, which can be specified by IP or DNS name

2. Host group (host group): a logical container of a host, which can contain hosts and templates, but hosts and templates within the same organization cannot be linked to each other. Host groups are usually used when assigning monitoring permissions to users or user groups

3. Item: data related to a specific monitoring index; these data come from monitored objects; item is the core of data collection in zabbix. Relative to a monitoring object, each item is identified by "key".

4. Trigger: an expression used to evaluate whether the data received within a specific item of a monitoring object is within a reasonable range, that is, the threshold; when the amount of data received is greater than the threshold, the state of the trigger will change from "OK" to "Problem", and then to "OK" when the data is restored to a reasonable range again

5. Event: triggers an event of concern, such as trigger state transition, automatic registration of a new agent or re-online agent, etc.

6. Action: a pre-defined method of handling a specific event, such as sending a notification and when to perform an action

7. Alarm upgrade (escalation): a custom scheme for sending alerts or executing remote commands, such as sending alerts every 5 minutes, a total of 5 times, etc.

8. Media: a means or channel for sending notifications, such as Email, Jabber, SMS, etc.

9. Notification: information about an event sent to the user through a selected medium

10. Remote command (remote command): a predefined command that can be executed automatically when the monitored host is under certain conditions

11. Template: a collection of preset entries used to quickly define a monitored host, which usually contains item, trigger, graph, screen, application, and low-level discovery rule; templates that can be linked directly to a host

12. Application: a collection of item

13. Web scenario (web scennario): a live multiple HTTP request used to test the availability of a web site

14. Front end (frontend): web interface of Zabbix

The following figure is a flowchart of zabbix, which concatenates the relationships between terms.

Operation and maintenance monitoring tool zabbix overview of operation and maintenance monitoring tool zabbix IV. Monitoring architecture of zabbix

In the actual monitoring architecture, zabbix is divided into three architectures according to the network environment and monitoring scale: server-client, master-node-client and server-proxy-client.

Server-client architecture

Overview of Operation and maintenance Monitoring tool zabbix Overview of Operation and maintenance Monitoring tool zabbix

The picture above shows the server-client architecture, and it is also the simplest architecture of zabbix. The data exchange between the monitor computer and the monitored computer is carried out directly between zabbix server and zabbix agentd without any agent. It is suitable for monitoring environment where the network is relatively simple and the equipment is relatively few.

Server-proxy-client architecture

Overview of Operation and maintenance Monitoring tool zabbix Overview of Operation and maintenance Monitoring tool zabbix

The figure above shows the server-proxy-client architecture, in which proxy is a bridge between server and client. Proxy itself does not have a front end, and it does not store data itself, but temporarily stores the data sent by agentd, and then submits it to server. This architecture is often compared with the master-node-client architecture, and is generally suitable for the monitoring of medium-sized network architecture across computer rooms and networks.

Master-node-client architecture

Overview of Operation and maintenance Monitoring tool zabbix Overview of Operation and maintenance Monitoring tool zabbix

The image above shows the master-node-client architecture, which is the most complex monitoring architecture of zabbix and is suitable for large-scale environments with multiple devices and across networks and data centers. Each node is also a server, which can be connected to proxy or client directly under node. Node has its own configuration file and database, and what it needs to do is to synchronize configuration information and monitoring data to master. The failure of master may damage the integrity of the underlying architecture of node.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.