In this back-to-school season, it is time for revisions! Early this year, we have revamped the Centreon portfolio. Our products have been streamlined along with a much-thought out re-naming exercise to best reflect our roots, values and evolution of the Centreon brand and software.
Centreon Engine in the Future: Simpler is Better.
In the first part of this article, we saw the history of Centreon Engine, from his inception as a replacement to Nagios, to the mature software it is now. We saw some of the issues it has successfully responded to and its limits in struggling with a growingly old codebase. The future asked for improvements made to Centreon Engine, and more precisely, for a diet.
Centreon’s Coming of Age
Centreon’s early history is closely tied to Nagios. Indeed, Centreon Web started out as a solution to make Nagios less complex and easier to use while maintaining its powerful flexibility that made it a favorite of the industry.
Centreon has grown up considerably since, and while it has remained true to its root, we found the need to make substantial evolutions to Nagios on our own. This need led to the creation of Centreon Engine, the subject of this article.
Most users will never see this core software. Today Centreon’s software suite, known as CES, is a complete monitoring platform that includes the three big pivotal bricks: Centreon Web, Centreon Engine and Centreon Broker, together with all the tools needed to monitor any kind of IT system. CES has been downloaded and used by thousands already and has already proven its mark. This relative obscurity can generate a lack of interest, but just as the engine in a car is essential to the car, Centreon Engine is essential to Centreon CES.
The best way to understand this is to begin by the grandaddy of Centreon Engine: Nagios.