Reporting and misc rave.

[Tedman Eng]

Read/Write access to cmd.cgi can already be disabled using .htaccess


-----Original Message-----
From: Ton Voon [mailto:ton.voon at altinity.com]
Sent: Friday, February 03, 2006 6:19 AM
To: jim.pye at pyenet.co.nz
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] RE: Reporting and misc rave.




On 3 Feb 2006, at 00:59, Jim Pye wrote:


My wishlist for Nagios?
0) Two levels of access - readonly and manage - on a per contact, per
service level.  Dont just give 'manage' access to everyone listed as a
contact for that service.
True. I did work on a customers site where the management wanted access
to monitor what was going on but did not want to change or acknowledge
alerts etc.


I've been thinking of patching Nagios so that a contact can have defined: 


issue_commands = [0|1] (default 1 for backwards compatibility)


This way you can define a contact to be able to view a subset of all
hosts/services, but would not have access to write to cmd.cgi for downtimes,
reschedule, etc.


Would this go down well?


Ton




http://www.altinity.com
T: +44 (0)870 787 9243
F: +44 (0)845 280 1725
Skype: tonvoon


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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