<HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.5296.0" name=GENERATOR></HEAD> <BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma"> <DIV>I wish to pose a question to the group which may develop into a request for Nagios 3.0.</DIV> <DIV> </DIV> <DIV>First I should mention that my question pertains only to front-end view rights, not notifications. In the current CGI's if a contact_group is defined for a host that contact_group automatically gets view rights for ALL services associated with that host. Inversely if the contact_group is defined for a service (but not the host) they will be able to see the service (in status.cgi, extinfo.cgi, etc), but not the host (same cgi's). This has caused us some issues in that some people only want to see what services they are in charge of.</DIV> <DIV> </DIV> <DIV>Example: Host: Windows1, Services: Disk,CPU,Memory,HTTP,Ping. The server team wants to be able to view all services and the host, while the web development team only wants to see HTTP and the Host (so they know if HTTP is having a problem or if the host is down), and lastly the network team wants to see Ping and the Host.</DIV> <DIV> </DIV> <DIV>Unless I'm mistaken you can't do this in the current CGIs. I wondering if there isn't a better alternative. There are potentially 3 ways of allowing contact_groups to see various items in the front end. They are as follows:</DIV> <DIV> </DIV> <DIV>1. If a contact_group can see the Host, it can see ALL services--current model</DIV> <DIV>2. You must explicitly allow a contact_group for a host and any services it can see</DIV> <DIV>3. If a contact_group can see ANY service for a host, it can also see the host--inverse of current model</DIV> <DIV> </DIV> <DIV>Does anyone have any input on if requesting method 2 or 3 in nagios 3.0 is valid or not?</DIV> <DIV> </DIV> <DIV>Marlo Bell</DIV> <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>