setup a log file monitor for the apache access_log whenever anyone uses the ext command cgi's the apache log should give you the username and the http post data depending on how you configure apache, <div class="gmail_quote"> On Tue, Nov 17, 2009 at 7:50 PM, Frost, Mark {PBG} <<a href="mailto:mark.frost1@pepsi.com">mark.frost1@pepsi.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> We're looking at possibly allowing more individual users into the web interface and allowing them to schedule their own downtime. One concern is that if a team doesn't get an alert they could come to my team (the team that administers Nagios) and say "why didn't Nagios send us an alert when X was down?" when the issue was actually caused because a member of their own team had disabled notifications. I know we can see that an external command was executed in the log file and when, but there's no way of knowing (as far as I can see) who actually requested that that command be run. In my opinion, it could be useful to know that 'bob' requested that notifications be disabled on host X particularly as it pertains to the web interface. Is there a way to do this or would this need to be a feature request? Thanks Mark ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_blank">http://p.sf.net/sfu/bobj-july</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div>