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

Introduction to 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.

Zabbix consists of two parts, zabbix server and optional component zabbix agent.

Zabbix server can provide remote server / network status monitoring, data collection and other functions through SNMP,zabbix agent,ping, port monitoring and other methods. It can run on platforms such as Linux,Solaris,HP-UX,AIX,Free BSD,Open BSD,OS X.

Advantages of Zabbix:

1 supports distributed monitoring

(2) it has its own drawing function, which can obtain numerical data and generate graphs automatically.

3 Web configuration mode, easy to operate and use. It is very fast to add monitoring items or machines.

When there is an alarm, no matter in any interface, a small window will pop up to give an alarm, and there will be an alarm sound prompt at the same time, at the same time, you can quickly check the monitoring items.

5 it comes with rich built-in functions, and it also supports the call of scripts and nagios scripts.

6 when there is a problem, you can automatically execute the command remotely (you need to set the execution permission on agent)

Disadvantages of Zabbix:

1 it is not convenient to modify in batches, it can be assisted by database.

2 after in-depth, there are very few Chinese materials, most of the questions need to see the official documents and forums.

(3) lack of data summary function, if you can't view the average value of a set of servers, you can consider secondary development.

4. Compared with cacti, zabbix has poorer drawing function and more complex traffic acquisition.

Example 1:

Monitoring project

Key value setting:

Log [/ data/canal/logs/job-xxx-xxx/job-xxx-xxx.log, "caused | Exception | DRROR", skip,] yyyy-MM-dd hh:mm:SS

The content in this key value is, log absolute path, keyword, skip is to skip the old content, only monitor the newly generated logs, other unwritten ones are separated by ","

Trigger: problem expression: {aws-bigdata-canal-49-63:log [/ data/canal/logs/job-xxx-xxx/job-xxx-xxx.log, "caused | Exception | DRROR", skip,] .nodata (10s)} = 0 restore expression: {aws-bigdata-canal-49-63:log [/ data/canal/logs/job-xxx-xxx/job-xxx-xxx.log, "caused | Exception | DRROR", skip,] .nodata (2m)} = 1

Nodata (2m) this function has no data 1:true 0:false in 2 minutes. So if you get the keyword "caused | Exception | DRROR", the value of the nodata function will become false, which will trigger the trigger to achieve the purpose of monitoring!

# # example 2:

Usually, we will monitor some keywords and report errors directly, but there are often requirements keywords and some strings that can be combined with no problem, even if there are keywords such as error exception, and so on, we need to use powerful rules.

Monitoring projects:

Log [/ var/log/test_file.log, "Error | (?

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.