Centreon 2.0 - NDOutil PDF Print E-mail

 Version of Centreon : 2.0
Developer : Team Merethis
Contact : Julien Mathis - This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Technology : MySQL - C - XSLT/PHP

[Go back to Centreon 2.0 features page]

 Issue

 - On important architectures, the monitoring interface slows down because of the Nagios status file that is parsed continuously.
 - After the development of a system that could make the parsing faster, the solution had greatly improved. However, the refreshment speed of the data remains slow. 
 - As long as status are not stored in a database, it will not be possible to integrate Web 2.0 modules that make our solution much handier and easier to use (Ajax search engines, icones, tooltips etc...)

Solution

 After having spent several weeks running tests, we decided to use the NDOutils module developed by Ethan Galstad, developer of Nagios. NDO is a Nagios module that offers real time monitoring with status information that is directly stored in an SQL database. With this, there is no more need to read a status file everytime the monitoring is refreshed, which is what Nagios basically does.

 

 By combining NDO with XSLT / AJAX, we obtained better speed and fluidity. Here is an example ; in order to refresh a monitoring page on a server with 1000 services and 100 hosts, it would take about 4 to 6 seconds (depending on the server's specs) to display 50 lines. With the new solution, it takes 200ms only!

 

 

centreon_data_gathering500x343.png

 

 

 The reason why the performance has greatly improved is because with a database system, we do not have to read all the data of the database to determine a general status of the monitored IT.

 

 This technology will also allow us to use the status of services so that you can always keep an eye on your resources' status, no matter if you are configuring it or reading a report generated by Centreon. Status reminders will be added to Centreon in future versions.

 

 This technology will also allow us to gather the status of several servers placed in a central server. We used to need the NSCA (Nagios Service Check Acceptor) in order to use a shared architecture. The more monitored ressources you had on your central Nagios server, the more process would have been required due to refreshment of logs, status etc... Now, only the MySQL server and the NDO module will be affected. Nagios will then be able to fully take advantage of its performance for an optimized charge management.

 
[ Back ]
Latest News
Partners' News
Who's Online
We have 25 guests online

© 2007-2008 Centreon - Revisited Experience Of Nagios - Web Site -