This post is also available in: French
For many months now, members of the Centreon community have asked us to share good practices for monitoring with Centreon. So, we are pleased to begin a series of articles which should provide you all necessary information to use efficiently your favourite monitoring platform.
Centreon is a modular software that can adapt to a lot of contexts. You can use Centreon to monitor some network equipment or many servers or middleware in a datacenter. So, Centreon is flexible and has been conceived to meet different needs. This relative complexity can be disturbing. Thus, to successfully deploy your monitoring plat-form, you need to get a comprehensive view of the software.
We are going to describe and share some good practices related to Centreon. These practices have been presented and described by our experts. They are the people who deal best with all the problems related to the development and the use of Centreon. Our teams integrate Centreon in various contexts, within simple or complex architectures with huge or light monitoring scales.
Basically we will tackle several subjects such as:
– make full use of Centreon
– obtain optimum performance
– save your time
– make your life easier
Make full use of Centreon
Centreon has many features. We will provide some advices helping you to better use all the features. Each of them will be presented and analysed with some case-studies. We will explain some of the features that you don’t use just because you don’t know them! You will find some advices to avoid misuse of features as well. The macros of hosts and services are examples of features that you have to know and to use.
Obtain optimum performance
To obtain the best performance, we will bring you our own experiences related to huge and complex architectures and will explain some good practices. A monitoring plat-form needs several tools: Centreon, MySQL database, plugins, a schedule such as Nagios or Centreon Engine, a broker such as NDO or Centreon Broker and some monitoring agents. You can use these advises for each component or more generally to distributed architectures.
Save your time
Follow our good practices and save time! You have different ways:
-Not to waste time because you had to look for a feature you don’t know
-not to lose it because you had to change a part of the configuration after a wrong strategy
-maybe to spend a little time at the beginning to avoid to spend lot of time afterwards
-to modify a large numbers of elements in one time
Some advises about configuration strategy, configuration of monitoring or macro model will be brought to you.
Make your life easier
The objective of a monitoring plat-form is to make your life easier. Thanks to these advises, you won’t have to enter many times the information, to reconfigure your monitoring every months, to look for how you can optimize your plat-form or to check what behaviour for what parameters…
The next themes
The upcoming themes will be:
– to get out of services with hosts group
– service models
– hosts models
– macro based on host or service model
– how you can use properly hosts and services group