> Does the contact_groups section support inheritance or is that a version > 3.0 feature?
I don't think so, no. I don't know much about what's coming-up in version 3.0. > The problem with using a template (at least for us) is that we have a lot > of machines that have very specialized contact groups. Like 1-2 people for > this host, 1 person for that host, etc. For that, I build a small contact > group in to each host that requires it (e.g. cg_hostname) and then enter > the people in there. That's probably not a bad way of doing it. As people change responsibilities, it makes it easy to move people from one group to another. Another option would be just to have a contact_group for each person and specify multiple contact_groups for each host/service as required. > I'm not too fond of doing that, so if I could have the contact_groups in > the template *merge* with the contact_group in the host/service that would > be great. Or perhaps even allow individual contacts on hosts and services? I'm with you there; it would be nice if you could specify individual contacts rather than contact_groups in the host and service definitions. For most of us, though, having to specify contact_groups encourages a more sensible configuration. You can use the template to set a default set of contact_groups, which are then overridden if you specify the contact_group directive in the host or service definition. I don't know if that would help you a great deal though. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
