User Command Limitations

[jkbuster]

I've been looking for a way to limit certain individual commands to a small group of users, such as making it so that only 2 people can disable notifications for a host or service. But, everything I've found has been to enable/disable users from submitting any commands. I'm looking for a way to schedule downtime instead of just disabling notifications and forgetting to re-enable them.

--
Thanks,
JKB

[slansing]

Welcome to the community JKB,

Have you taken a look at these?:

Scheduled Downtime Search: http://exchange.nagios.org/directory/Ad ... d-Downtime

Scheduled Downtime Documentation: http://nagios.sourceforge.net/docs/nagioscore-3-en.pdf "Go to the Scheduling Downtime section"

[jkbuster]

slansing,

Thanks for the quick response! I have looked at the nagios documentation. The section you've referred me to is how to schedule downtime, I already do that. I'm trying to force others to do so as well. Instead they disable notifications, then forget to re-enable them when they are done and we're operating without any alerting system.

As for looking in exchange, I've already looked there. However, everything I found for scheduled downtime was for things like recurring downtime. I just want to remove the ability to disable notifications from all users except myself and a couple others, but not block people's ability to schedule downtime.

Based on what I've found, this doesn't exist. But, I figured I'd ask and see if anyone here knows of a solution I haven't found yet.

--
Thanks,
JKB

[lmiltchev]

I don't think this is possible. I would really like to know if someone comes with a solution.

[jsmurphy]

Haven't seen this question for a while, as lmiltchev pointed out it's not actually possible to get the functionality you are asking for. We had similar issues when we first deployed years back and decided it was primarily a user education problem... we ran short internal training sessions for our users to help them understand the impact of doing the wrong thing.

The team leaders would then lean on people who continued to do the wrong thing and within a month the problem disappeared.

Another solution that I've heard of was write a script that would check the ndo database for who disabled something and if it had been disabled for longer than 24 hours it would email them asking them to fix it.

[slansing]

Thanks for the info from a real life case and tips Jsmurphy. I'm going to mark this as resolved but leave it open for a bit to see if jkbuster has anymore questions.

[jkbuster]

Yes, thanks jsmurphy! I figured that would be the case, but I thought I'd ask. We're beginning our education process, but the ability to force this would be helpful.

Thanks again!

--
JKB