Nagios: How to allow a non-admin user the correct permissions to be able to acknowledge alerts

nagios

Sometimes there are alerts which are not so urgent and can wait for the next morning until they are taken cared of.
During these times, the NOC team keeps getting alerts regarding the problematic issues but have no access to acknowledge them.

I've went through the cgi.cfg file which controls user permissions in Nagios but I couldn't find the directive which talks about alert ack's even though I read the whole file.

Can you please point me to the correct directive to set?

Thanks in advance

Best Answer

Unless you override the behavior by adding them to authorized_for_<whatever> options in cgi.cfg, users can only see or interact with hosts/services for which they are contacts.

Users also get alerts for hosts/services for which they are contacts. So, if a user gets an alert, that user can also acknowledge the alert.

All of this depends on your users logging into the web interface with their own usernames, which must match the contact names. This works well with LDAP authentication, for example.

Related Solutions

How to make nagios send me brief and informative alerts

Nagios can be configured to send notifications by various ways and in various formats. If you need to personalize that please refer to your commands.cfg.
This is an example to show you how to receive a short notification by sms using gnokii:


define command{
        command_name    notify-host-by-sms
        command_line    /usr/bin/printf "%.120s" "$HOSTALIAS$ is $HOSTSTATE$" |/usr/local/bin/gnokii --sendsms $CONTACTPAGER$ -r
        }

define command{
        command_name    notify-service-by-sms
        command_line    /usr/bin/printf "%.120s" "$HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$" | /usr/local/bin/gnokii --sendsms $CONTACTPAGER$ -r
        }

The output is like this "hostname is up"

The correct way to stop the nagios ndo2db daemon

I found the culprit - it was Centreon's config file builder.

ndo2db has a lock_file setting which is missing from the Centreon config UI.

When Centreon generates the config files it also generates ndo2db.cfg - but without the lock_file configuration value.

There's an open issue about this:

No lock_file field in Configuration - Centreon - ndo2db.cfg

Having spelunked the source code, when ndo2db daemonises and if there isn't a lock_file setting then it ignores this and carries on and no lock file is written containing the PID.

This of course means that the stop function in the init script won't be able to identify the ndo2db process id so it can be killed.

Update:

To resolve this issue I manually added a new column to the cfg_ndo2db table in the centreon database:

ALTER TABLE `cfg_ndo2db`
    ADD COLUMN `lock_file` VARCHAR(255) NULL DEFAULT NULL;

I then populated it with the path of my ndo2db lock file:

UPDATE `cfg_ndo2db` SET `lock_file`='/usr/local/nagios/var/ndo2db.lock' WHERE `id`=1;

This will force centreon to write the lock_file setting each time the config is generated. This also appears to survive upgrades as well, though I'd always check the database upgrade scripts to ensure this doesn't sneak in as an undocumented fix.

Best Answer

Related Solutions

How to make nagios send me brief and informative alerts

The correct way to stop the nagios ndo2db daemon

Related Topic