Nagios version used: 3.0.6b
We define a contact_groups field in our hosts definition called say "host-admins". We define a contacts field (and -no- contact_groups field) on a service definition monitoring a service on the host. Because the implied inheritance feature for contact_groups ignores the fact that a contacts field -is- defined on the service definition (and that should be enough IMHO no?), -service- alerts also get sent to the hosts's contact_groups recipients...which annoys them as they don't consider the application's service monitorings "their problem".
The doc show a nice way to cancel -template- inheritance. Give the field the the keyword value null. I thought it would be nice if I could define the contact_groups field in the service and give it the keyword null as the value to cancel the implied inheritance of contact_groups from the host also. No joy. Perhaps an enhancement? Or perhaps having a contacts field defined be enough to override implied inheritance of contact_groups from the host?
Anyway my hack workaround was to define a contacts_group called "bitBucket_group" with a dummy contact as a member with an email address which mails to a /dev/null mailbox. So now I define contact_groups in my service template and give the field the value of bitBucket_group. Crude, but effective. Of course this lets me override the field in the service definition itself in those cases where I do want the field with real recipients.
First post here and searched first but found no related thread so apologies if I missed it. Otherwise if you've thoughts/better idea or need to tell me I'm drowning in a drop of water I would be much obliged.