Host Alert Contact Inheritance to Services

[dworthcsl]

Hi,

I am trying to add a contact that just gets paged for critical service events as well as host down. I am controlling this by using templates. For services, I have a separate template for each check. In specific templates, I will add the pager user. So for example, I have the following:

check-disk-template > admins and pager
check-cpu-template > admins
check-logfiles-templates > admins and pager

Those templates are then inherited in to the corresponding service checks. Notifications will go out to the admin group for all of them, but only the disk and log files check for the pager user.

I also have separate templates for hosts. They are split according to the type of host it is. i.e. SAP, web, xyz application, etc. I define notification contacts in these templates. Host that belongs to these groups will inherit the contacts from these templates. The pager user is assigned to all hosts. That way we can receive a page if a host goes down.

The issue I am running into is that the service that does not pull in the pager contact from the template still sends out notifications to the pager user. I was able to determine that it is pulling it from the host template. Is this the desired functionality? Service can inherit contacts and other settings from the host templates or configs? Is there a way around this?

I am running xi 2011 r3.3 running on RHEL 6.x 64.

Thanks for your help,
David

[scottwilkerson]

Is is a contact_group assigned to the host? If so this is expected behavior
http://nagios.sourceforge.net/docs/3_0/ ... tance.html

[dworthcsl]

It is a single contact that gets assigned to a host by a host template. Is there a way to keep host contacts/contact-groups separate from services? The requirements are to have the pager contact get notified for all host down, but only receive critical alerts for only certain service checks.

[scottwilkerson]

Individual contacts added to the host shouldn't issue service notifications, however contact hosts do. the section of importance on this issue in the documentation is under "Implied Inheritance" about 2/3 the way down the page.