In the previous article of this series, we outlined some key monitoring enhancements that are now part of CES 3.2, including updates of the ISO file to make installation and configuration even easier.
In this short and final article, you’ll find out how simple and quick installing CES (Centreon Enterprise Server) can be. In fact, the installation procedure can take as little as an hour at no cost, especially if your storage infrastructure does not create bottlenecks for disk access. That means you can try and test it out for as long as you want.
Don’t believe us? Try it for yourself.
“One of the nicest things about choosing CES is knowing we’ll be able to evolve and scale IT monitoring in an affordable and effortless way as our needs and those of our customers, grow over time,” –
Sebastien Boulianne, network and system administrator at CPU.
We mentioned it a few weeks ago on our blog and we did it : the official repository of Centreon plugins are now on GitHub. We hope this will encourage more of your contributions. You can still have access to Forge Centreon but trouble tickets or bugs are now open on GitHub.
How to contribute ? Continue reading
With the release of CES version 3.2 recently, we explained the difference between Centreon software and CES. To recap, CES is our industry-grade enterprise solution that groups a large set of key monitoring benefits made possible by the Centreon software suite.
In this 2nd part, we summarize some key benefits that are now part of CES 3.2, the third version of CES 3.x based on Cent0S 6.x. It obviously integrates all system updates provided by CentOS.
In 2012, we presented the best practices for developing a monitoring plugin for your Centreon platform. Meanwhile, our team has developed a new ecosystem called “Centreon Plugins” to management monitoring plugins.
Although the previous article is no longer relevant, the basic concepts of development are still those in force:
- return code of host’s plugin (UP, DOWN, UNREACHABLE, UNKNOWN) ;
- return code of service’s plugin (OK, WARNING, CRITICAL, UNKNOWN) ;
- output’s management (output également appelé short output, et long output) ;
- perfdata’s management ;
Today, we created an ecosystem based on:
- main script (« centreon_plugin.pl ») ;
- libraries for hardware, os, network equipment, storage, databases or applications ;
- each libraries has a list of indicators to monitor.