Two development of Nagios for enterprise-level monitoring platform development (VII)

Development background:

A company has a lot of servers (>3000), each server has different purposes, such as DB Server, WEB Server, ESXi, and so on, each group use one of them, each group may have more than one server administrator. Now the problem comes out, how to centralize the management of these servers, how to properly allocate resources to the server, how to get the running state of each server, how to understand the service situation of each server running, how to expand the different or re-purchase server according to the use of resources .... Many problems with the increasing number of servers, the use of a variety of applications came into being. So, the platform I'm describing now is about solving the problem.

Current Status:

Perhaps many ops will say, now is not there a lot of mature monitoring tools? Just use one, please. So, is the monitoring tool now meeting your business status? Can you make effective permission controls for your company's internal structure? So we can't rely entirely on existing tools, we have to create our own things.

Platform Introduction:

function, all of the above can be solved. The implementation principle, which has been published before, is of course based on Nagios. Bottlenecks, that is also the bottleneck of Nagios, performance temporarily not outstanding, ease of use, but also can, not too much trouble, technology, can not break through the bottom of CGI and Nagios. It's just a layer of skin, but what if you think it's easy to get C/php/java together? Then I'll take you too. Every tool or platform has a place where people spit, which is normal.

Function:

1. Monitoring server hardware and software information, CPU, memory, disk, network operation status, the operation of the Web service, the service port unblocked can also be monitored, and do not need to install the client;

2. Monitoring of abnormal results can be mail alarm, so that the first time to tell you which server or service (port exceptions, hardware anomalies) have problems;

3. The application of the server deployment can be automatic or manual start and stop, automatic meaning is the state of the timing monitoring service, found to stop immediately start up, to ensure the accurate and efficient operation of services;

4. Can clean up the log, automatic or manual can, timely release the server disk space is very useful;

5. Manage the ownership of servers and services, facilitate the management of inquiries and principals;

6. Group control, each group can manage their own server and service information;

7. Sub-authority management, divided the visitors, administrators, system administrators three roles,

8. Other you can think of or unexpected.

Display diagram:

Please respect the results of the authors, reproduced when the source.

Comments and suggestions: [email protected]

Two development of Nagios for enterprise-level monitoring platform development (VII)