Comparison between monitoring treasure and zenoss, zenoss monitoring

Comparison between monitoring treasure and zenoss, zenoss monitoring

After graduation, I came to my current company and started O & M. When we first arrived, our project had only 10 servers, single point mysql server and web server. After nearly three years, the project now has three DataCenter and more than one hundred servers, mysql Sync and more than a dozen web servers between the three DC servers. Monitoring of so many servers and services is a crucial link. We are concerned about how to monitor server performance, how to promptly discover mysql sync problems, and how to implement automatic alarms. At the beginning of my work, I paid attention to this content and came into contact with the monitoring site. It has been nearly three years since then. In this process, we also use the Open Source Monitoring Software zenoss to establish our own monitoring system, use monitis to monitor the status of our website, and use jmx and ganglia to monitor hadoop systems, and write programs to monitor the health status of mysql. Here is a brief introduction of the characteristics of the monitoring and zenoss I know and a simple comparison.

1. Overview

The first monitoring site that has been exposed is a monitored website that can monitor website performance, server performance, and service performance (including the monitoring of mysql that we are most interested in ), it also provides a series of excellent user experience functions such as custom alarms and export views.

Zenoss is an open-source enterprise-level monitoring software. It mainly monitors server performance, network and application level. Zenoss has powerful functions and can also generate custom alarms and reports.

From the perspective of the interface, the interface design of the monitoring site is more exquisite and the user experience is relatively good. However, zenoss is added to google map, which intuitively shows the location of servers and the location of servers with errors. This function is useful for cross-region and cross-DC projects.

2. server performance monitoring

Both cloudmonitor and zenoss can use snmp to monitor server performance. The configuration method is basically the same as the method used. It is easy to add servers. Compared with cloudmonitor, zenoss provides a function to add servers in batches. You can manually add multiple servers at a time or add all servers in the same subnet. Sometimes we will add a subnet's staging environment. If you delete it later, you can use this method to batch add servers.

In the process of configuring snmp, two points are worth noting. First, change community. Do not use the default public. Everyone on Earth knows. The second is to add a new view that can access the MIB node you need to monitor. For the sake of simplicity, we configure the view systemview embedded on the server. 1. This configuration allows the community to access all MIB.

In addition, I think it is a little dangerous to directly access server information through snmp.

3. MySQL monitoring

Because all the results and services of our project depend on mysql, and we have created a two-way synchronization mysql master in three different DC, each mysql master has 4-6 additional slave instances. Therefore, the mysql architecture is relatively complex. Due to network problems and writing volumes, the query volume increases, and mysql performance and health status are an important aspect of our concern.

The monitoring platform can monitor mysql in two ways. One is to directly establish a user with certain permissions on the mysql server to provide the monitoring platform. Through this user, the monitoring platform can monitor the basic performance of mysql, such as query throughput, current connections, and memory. The other is monitoring through the MySQL plug-in. It can also collect various performance indicators of the MySQL database. Zenoss also provides a built-in mysql monitoring template. You can directly add this template to monitor mysql memory, network, query, and other indicators.

The advantage of monitoring mysql is that it is easy to add and monitor, and the monitoring content is relatively comprehensive (the table locks we care about will also involve statistics ), you can create a separate mysql service monitoring without relying on the monitoring of the mysql server. However, it has a defect that we cannot customize the content we need to monitor. For example, we are very concerned about the latency of synchronizing mysql master from mysql slave. Relatively speaking, zenoss must first add the mysql server to add the mysql service, but its advantage is that in addition to the default monitoring content, we can write the content required for script statistics by ourselves, the result of zenoss regularly reading this script is displayed on the page. You can also customize alarms based on the data currently collected by the script.

4. website monitoring

What attracts me most is the website monitoring. Although zenoss can also monitor server-level information by adding web servers, we need to know the health status of our website in different network environments. Cloudmonitor provides this function. Among them, I think it is quite good that we can select different monitoring sites to learn about the corresponding situation of our website at different monitoring sites. These monitoring sites are also part of overseas sites. This is useful for cross-region users in our project. We will also use monitis for monitoring, which is comparable to monitis.

5. Alarm Mechanism

Both cloudmonitor and zenoss provide a variety of alarm methods, such as email and SMS. The mail method is very simple, and the two settings are similar. For short messages, zenoss needs to set up the SMS Server to send short messages, which is complicated. In addition, the monitoring platform also supports mobile terminals, MSN, GTalk, and URL callback methods. The options are diverse and easy to set.

6. Summary

Cloudmonitor and zenoss can meet our daily monitoring needs for servers, services, websites, and so on. The advantage of cloudmonitor is that the interface is exquisite, the user experience is good, and the website monitoring function is powerful. The disadvantage is that you cannot customize script monitoring except the default content. Zenoss has the advantage of being open-source, allowing custom scripts to monitor any content we want to monitor. The disadvantage is that it requires some experience in installation and use, and the interface is relatively rough.