So I'm following up on this, I may not have described it right. If you define a contact for a host it because a default contact for a service of that host. Is there any way to turn that behavior off? Because I want to know a host is down, and have it page people, but I don't want some of the services associated with the host to do the same thing, they are going to send notifications through a different method (that doesn't wake me up at night, because they aren't that important.) I suppose I could just explicit the contact on the service to override the default from the host definition.
On Mon, Jul 14, 2014 at 9:09 PM, Dale Harris <rod...@gmail.com> wrote: > Hi, > > I'm working with Icinga 1.11.4. I noticed when I trying to set a > contact for a host that that contact was being assigned to the > services associated with the host, so the services basically appeared > to be inheriting the contact information. Is that the way it is > supposed to work? I have few select services and host status > notifications that I would like to send to PagerDuty, and some > services I don't want to go there, but I don't seem to have that level > of granular control that I would like. Unless I have go through and > mask out the contact in each service I don't want, but that is kind of > pain. > > -- > Dale Harris > rod...@maybe.org > rod...@gmail.com > /.-) -- Dale Harris rod...@maybe.org rod...@gmail.com /.-) _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
