Page 1 of 1

Service notifications

Posted: Wed Jul 10, 2013 2:21 pm
by masmith
OK have done a little looking and I appoligze if i over looked the answer to this question.

Here is my problem. Hopefully it is just me over looking that answer.

NagioXI ver 2012R2.2

Everything is working as planned and designed just have one items that is bugging me that i can find a better way to do it.

This problem exist in a few different scenarios for me. but will stick to a singe one.

I have creates a service "Service 1" in this service i have attached multiple host "Host 1", "Host 2" ,"Host 3" and attached multiple contacts " Contact 1",Contact 2", "Contact 3".

The problem comes when "Contact 4" needs to be alerted for "Service 1" on "Host 2" only.

Is there a way to assign a contact to a service for a specific host when you are using a generic service with multiple host attached?


I hope that makes sense. if not let em know and i will see if i can clarify it

Thanks
Marc Smith

Re: Service notifications

Posted: Wed Jul 10, 2013 4:01 pm
by lmiltchev
You can use Service Escalations (CCM->Service Escalations) in order to achieve this. Add new service escalation, click on "Manage Hosts" and select "Host 2". Click on Manage Services and select "Service 1". Set "First Notification" to 1, "Last Notification" to some high number, "Notification Interval" to 60, select the "Escalation Options" that you need (w,u,c,r), click on "Manage Contacts" and select all four contacts. Click on "Save" and "Apply Configuration".

Hope this helps.

Re: Service notifications

Posted: Thu Jul 11, 2013 8:04 am
by masmith
Just a quick question?

Do the service esculation override a notification set at the service level?

Re: Service notifications

Posted: Thu Jul 11, 2013 10:00 am
by lmiltchev
I will, when the escalation kicks on. This depends on what number you've set for a "first notification".
Serviceescalation - first notification

This directive is a number that identifies the first notification for which this escalation is effective. For instance, if you set this value to 3, this escalation will only be used if the service is in a non-OK state long enough for a third notification to go out.