NagVis Screenshot or Read-Only Maps

[Mohr James]

> -----Ursprüngliche Nachricht-----
> Von: Valdinger, Stephen (DOV, MSX) [mailto:svalding at doverchem.com] 
> Gesendet: Mittwoch, 9. Juli 2008 20:27
> An: Mohr James; nagios-users at lists.sourceforge.net
> Betreff: Re: [Nagios-users] NagVis Screenshot or Read-Only Maps
> 
> We do this by giving the user a login to nagvis. They can 
> click the services to view them in the web interface but in 
> cgi.cfg we have given them no rights to manipulate them, so 
> the get the loely oopsy!  
<SNIP>

My boss is not too happy with that solution (I assume you mean not listing them as contacts for the respective services) Everything has to absolutely 100% clean and giving them an error message for is not "clean". 

I have been considering a feature request for an upcoming version. As more and more companies are using Nagios in general as well as the various add-ons, there is a growing need for dealing with multiple customers within a single Nagios instance. I would like to see finer control over who can do what. Something as "simple" as a new option "is_admin" for the contact objects that would activate/deactive the Host/Server Commands would be useful. 

Things like SLA reporting are needed, as well. There are a couple of companies working on products (commercial as far as I know). However, I am not aware of any that are ready for prime time.

Regards,

Jim Mohr

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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