Page 1 of 1

Hide the "Disable Notifications" link for hosts and services

Posted: Wed May 25, 2016 9:09 am
by romeor
Hi,

Is it possible?

Re: Hide the "Disable Notifications" link for hosts and serv

Posted: Wed May 25, 2016 10:47 am
by rkennedy
Can you show us the link you're referring to with a screenshot? I'd like to see what page you're talking about exactly.

Re: Hide the "Disable Notifications" link for hosts and serv

Posted: Thu May 26, 2016 2:45 am
by romeor
Sure. These are screenshots of older and newer nagios.

These links are part of commands.cgi file, which is compiled code (c I guess?). So the only possibility is to change the source and build nagios from sources? This should be done easier :) From the cgi.conf I can disable access to all the commands for specified user, but this is not what we would like to have. The disable notification button / link is pretty crazy for some installations (we use nagios as reporting engine for our service desk and it sends notifications there over custom command (basically via http post) and sends mails to admins. But our support sometimes disables the notifications even before the hard state arrived, as nagios starts yelling on state change. Can't disable the sound also, because it just forces people to react. They've worked a lot with disable notification button/link and now it is just a bad habit, which we can't rid of. So we see multiple variations here:

1. hide the disable notification button/link for all or specified users in cgi.conf
2. enable sound notifications in nagios only when hard state arrived
3. if we've reached the 2, then notifications should be automatically enabled after the host has changed its state to OK again, or at least admins should have a possibility to allow such behavior.
4. add new button/link - disable sound notifications for host/service :)
notif.png

Re: Hide the "Disable Notifications" link for hosts and serv

Posted: Thu May 26, 2016 5:09 pm
by rkennedy
The only way to remove those links is going to be by modifying the CGI files. If you'd like to suggest it be changed differently, feel free to raise an issue on the Core development GitHub.
https://github.com/NagiosEnterprises/nagioscore/issues

You might be able to do an apache rewrite rule, to lock people out of that page, but you'd have to look into writing it up.