How to handle multiple notification

  • 2 December 2021
  • 8 replies
  • 162 views

Userlevel 1
Badge +2

Hello !

We used centreon open source in our company and I have one difficulty with the notification.

We have one central for production servers and another for everything else.

Off production we have multiple environment like (development, qualification, integration and so on….)

We needs to notifiy different service or people on some service depending on the environment.

For example:

When a queue rabbit is critical on dev notify dev teams.

On qualification notify the business team of this environment etc…

Today with the heritage of service template I didn’t found a valid solution.

The only thing I find to manage my needs is to manage individually notification in service by host menu, service by service, but when you have hundreds edit it through the interface can take a lot of time.

And I think it’s not so visual to see the notification process.

The needs of sending the notification is established case by case so I cannot having a predefined list of people to notify.

What is the best way to manage that ?

If the solution of editing service by host is the only one I will write a script to manage this in the best way.


8 replies

Userlevel 6
Badge +19

Hi @mullergg 

I think you should give a try to escalation. This is not the original purpose of this feature but it could definitely help to work around your problem. 

Instead of managing at host, service or templates, you can manage by contact groups, hostgroups etc… 

 

 

Take a look and let me know, 
Cheers
Simon

Userlevel 1
Badge +2

But with this solution we cannot avoid for the default contact group to have the first notification ?

But it seems to be a good solution, I will try this.

Thanks.

Userlevel 6
Badge +19

But with this solution we cannot avoid for the default contact group to have the first notification ?

But it seems to be a good solution, I will try this.

Thanks.

Not sure I understand, but I didn’t mention that you should not mix notification rules at host/service/templates level with escalations. Solutions are mutually exclusive. 

Userlevel 1
Badge +2

Yes I understodd your point.

But to notify by default for every service I had to set up notification with host and service template.

And then set up escalation based on hostgroups / servicegroups to notify dev team on some service or host.

But in this case the default team and dev team will receive a notification.

And I only wanted to notify dev team.

Or is it possible to only set up escalation and it will notify by this process instead of default service / host template ?

Userlevel 6
Badge +18

...

Today with the heritage of service template I didn’t found a valid solution.

...

You may define a generic-service-acive-dev, generic-service-acive-prod, etc based on generic-acrive-service and define notification for each environment.

Then you need to inherite prod services from generic-service-acive-prod, etc.

what do you think?

Userlevel 1
Badge +2

...

Today with the heritage of service template I didn’t found a valid solution.

...

You may define a generic-service-acive-dev, generic-service-acive-prod, etc based on generic-acrive-service and define notification for each environment.

Then you need to inherite prod services from generic-service-acive-prod, etc.

what do you think?

I initially planned this option, but for example a cpu service is the same for all environment, with this option I need to set up a service_cpu_dev service_cpu_prod and so on.

This option will be too difficult to maintain.

Userlevel 6
Badge +19

and it will notify by this process instead of default service / host template ?

Yes you can manage all notification parmaters through escalation without defining any contact or group at the template level. 

Userlevel 1
Badge +2

Ok I will try that, thanks a lot.

Reply