O & M monitoring Nagios serialization: an important strategy for key application monitoring

Article Title: O & M monitoring Nagios serialization: an important strategy for key application monitoring. 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)

In other words, to do a good job, you must first sharpen the tool. To do a good job of system management and make your work 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
Linux.chinaitlab.com/server/778527.html "> http://linux.chinaitlab.com/server/778527.html
O & M monitoring Nagios serialization 2: deploying an apache server
Http://linux.chinaitlab.com/server/778738.html
O & M monitoring Nagios serialization 3: deploying and configuring the Nagios Service
Http://linux.chinaitlab.com/server/778739.html
O & M monitoring Nagios serialization 4: Nagios monitoring mysql Server
Http://linux.chinaitlab.com/server/778854.html
O & M monitoring Nagios serialization 5: Important policies for key application monitoring

Some time ago, someone asked me how to use nagios to monitor linux memory usage and how to set the alarm threshold? During linux running, memory is the most likely to be used. monitoring this object has no practical significance and is obviously an invalid monitoring policy. another person said: "The monitoring system sent alarm messages are endless at night... ". It is self-evident that this is also a bad monitoring policy. In fact, monitoring has lost its meaning. Therefore, a good strategy is necessary to make the monitoring platform more effective. So how can we be a good strategy? Here I will talk about some of my views based on my actual situation and hope to help you.

　　Policy 1: select a Monitored object

In a large network, the Monitored Objects may include servers, firewalls, switches, routers, and other devices, as well as services running on various objects. However, we do not need to put all objects in this monitoring system. For example, putting some test systems in monitoring will cause the trouble that the man above received the alarm text message throughout the night. Therefore, selecting the right monitoring object is the prerequisite for implementing effective monitoring. I personally suggest that only those objects with high importance cannot stop the service at will ?? Such as online transaction system ?? Is the object worth monitoring. Of course, server users always want you to monitor it, even if it is not so important.

Policy 2: Fault Alarm Method Selection

The boss hopes that we will sit on the computer tirelessly, but he is just wishful thinking. A proper fault warning mechanism must be provided for the monitoring system. Currently, common alarm mechanisms include email, SMS, msn, and web page display. Among these methods, SMS alarm is the best. In our sleep at night, we can't receive emails at any time, but text messages can wake us up and inform us that a fault has occurred, and before the boss and users find this fault. For organizations without channels, leasing sp services is a safer way. Other methods such as mobile Feixin are not well tested and are not suitable for key business operations. In addition, I used a small trick to let the monitoring platform send me a text message every afternoon, no matter whether there is any fault, so that I can know whether the text message interface is normal.

[1] [2] Next page