<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">I think I miss posted this last week, sorry for the dup if you get one.<BR> <BR>Ethan, et all:<BR> <BR>It would be nice in Nagios 3.0 to have a little more granularity in assigning contacts to hosts/service. Namely, if a particular person wants notified for a particular service, but the entire team doesn't need those notifications--the only option seems to be to create a new contact group with that one person a member and tie that group to the service. It would be nice if you could tie a singular contact to a host/service. Perhaps you could allow both directives like this:<BR> <BR>define serivce {<BR>service_description ping<BR>...<BR>contacts joeblow,janedoe<BR>contactgroups network-engineers<BR>...<BR>}<BR> <BR>On that same vein it is nice to have the granularity when assigning contact groups to services and hosts
directly (like in Nagios 2.x), but it was sometimes useful to tie a contact group to a ho
st group
(like in Nagios 1.x) or service group. Perhaps this could also be allowed. See the following:<BR> <BR>define serivce {<BR>service_description ping<BR>...<BR>contacts joeblow,janedoe<BR>contactgroups network-engineers<BR>servicegroups ping-services<BR>...<BR>}<BR> <BR>define serivcegroup {<BR>sevicegroup_name ping-services<BR>...<BR>contacts johndoe<BR>contactgroups network-operations<BR>}<BR> <BR>It is a little more complex, but in this way you could be as granular as you needed, but still be able to use grouping to your advantage.<BR> <BR>Marlo
<P><pre wrap>------------------------------------------------------------------------------
<P><pre wrap><width=80>
NOTICE: This email message is for the sole use of the<br> intended recipient(s) and may contain confidential and<br> privileged information. Any unauthorized review, use,<br> disclosure or distribution is prohibited. If you are not the<br> intended recipient, please contact the sender by reply email<br> and destroy all copies of the original message.
</pre></P>
------------------------------------------------------------------------------
</pre></P></BODY></HTML>