Tobias Klausmann wrote: > The altinity people have created a patch for the "view some, > change none" scenario[0]. Unfortunately, what I'd need is a > mechanism for the "view some, change a few" scenario I outlined > above. Is that to say that "view _all_, change some" wouldn't work for you? That's how we're working at present, out-of-the-box. While restricting viewing might reduce mental clutter for those concerned*, I can't see why being able to see everything is a big deal (unless you're displaying some super sensitive information in Nagios which is a totally different topic).
See http://nagios.sourceforge.net/docs/2_0/configcgi.html#authorized_for_all_hosts and http://nagios.sourceforge.net/docs/2_0/configcgi.html#authorized_for_all_services. *Our service centre can see everything, but we used service groups to provide "rolled up" views to keep it simple for them. All our engineers can see everything so when they spot an issue with someone elses kits that impacts their own, they can find out what the issue is and who to poke in the eye with a burnt stick to get it fixed. We found that trying to hide stuff just blinkered people and made them only responsive to their own issues ("not my server. not my problem.") which results in poor customer service at the end of the day. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ 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
