O & M monitoring serialization: full solution to nagios, an open-source monitoring tool

Article Title: O & M monitoring serialization: A Powerful open-source monitoring tool nagios. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

Source: it168

Author: Tian Yi (sery@163.com)

As the saying goes: to do good things, you must first sharpen your tools. to make system management easier and more effective, a good monitoring tool is essential. here, I recommend nagios, an open-source monitoring tool that has been used for more than four years and is powerful and customizable.

O & M monitoring Nagios serialization 1: self-monitoring implementation of Nagios servers
O & M monitoring Nagios serialization 2: deploying an apache server
O & M monitoring Nagios serialization 3: deploying and configuring the Nagios Service
O & M monitoring Nagios serialization 4: Nagios monitoring mysql Server
O & M monitoring Nagios serialization 5: Important policies for key application monitoring

As the saying goes: to do good things, you must first sharpen your tools. to make system management easier and more effective, a good monitoring tool is essential. here, I recommend nagios, an open-source monitoring tool that has been used for more than four years and is powerful and customizable.

First, let's look at the objects to be monitored in actual work? Here I have summarized two types of monitoring objects: NETWORK SERVICE monitoring and host resource monitoring. Network service monitoring can include host survival check, web Service monitoring, ftp service Monitoring, Database Service monitoring, and custom service monitoring; host resource monitoring includes system load, current ip address connections, disk space usage, current process count, and custom resource monitoring.

Next, let's look at the manifestation of nagios monitoring. The main purpose of monitoring is to promptly notify relevant personnel when the Monitored object encounters a fault or resource shortage, so that the problem can be quickly handled. The goal is to "receive timely and effective notifications before the boss and the customer discover problems". Assuming that the fault notification comes from the boss, I don't think everyone will be happy. Nagios provides at least three methods to facilitate our management:
1. web mode, that is, viewing Monitored Objects through a browser. In normal state, the status is filled in blue and an OK is displayed.
2. Email Notification: When a fault occurs, the system sends an email to the administrator or related personnel after the Set retry times and detection interval are reached to report the general situation of the problem.
3. Mobile phone text messages are very useful and timely. during sleep at night, it is no longer possible to view web pages or check emails. Once a fault occurs, text messages can wake you up at any time.
Generally, these three tasks are performed simultaneously: open a browser during work hours to view the page display, open the mail program, regularly receive emails, and the mobile phone is online 24 hours a day.

Finally, we use a real scenario to demonstrate the powerful functions of nagios, hoping to help you manage your system.

Scenario Description
For ease of Problem description, we assume that five servers (web servers, database servers, email servers, and nfs file sharing servers) need to monitor the services of several servers, monitor the resource usage of each server at the same time, this includes four items: load, disk partition usage, total number of processes, and number of current ip connections (you can also write a script to monitor more resource objects ). In addition to system administrators, these servers also have other users (such as programmers) who maintain their respective Servers. When a fault occurs, programmers who maintain the website can receive alarm emails and text messages, the Administrator does not need to receive these alarms. At the same time, users who maintain the program can log on to the monitoring server with their own accounts, view the status of the server on the web (you can only view the status of the server under the jurisdiction of others ).

Through the above description, we can organize the following table:

Machine name	Role	Users who can view status and receive alarm information	Required tools
Nagios Server	Monitoring end	System Administrator (SA)	Apache, nagios, nagios plugin, sendmail, perl, etc.
Email server	Monitored end	System Administrator and email administrator	Nrpe, nagios plugin, custom scripts, etc.
Database Server	Monitored end	System Administrator, dba	Nrpe, nagios plugin, custom scripts, etc.
Web Server	Monitored end	System Administrator, webmaster	Nrpe, nagios plugin, custom scripts, etc.
Nfs Shared Server	Monitored end	System Administrator	Nrpe, nagios plugin, custom scripts, etc.
Cache Server (squid)	Monitored end	System Administrator, webmaster	Nrpe, nagios plugin, custom scripts, etc.

After nagios and the monitored machine are configured, the basic output in the browser is similar:

[1] [2] [3] Next page