after upgrade to 5.11.2 only admin users can acknowledge alerts

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
NormaLaMonica
Posts: 3
Joined: Tue Jan 26, 2021 3:05 pm
Location: Tallahassee Florida

after upgrade to 5.11.2 only admin users can acknowledge alerts

Post by NormaLaMonica »

after upgrading Nagios XI to 5.11.2 from 5.11.1, only admin users can acknowledge alerts.
cyllenejb
Posts: 2
Joined: Fri Nov 05, 2021 4:20 am

Re: after upgrade to 5.11.2 only admin users can acknowledge alerts

Post by cyllenejb »

Hi,
After upgrade we found that only users with a contact name are authorized to acknloedge alerts.

In a change log, we don't see this new feature

Regards
Kamay21
Posts: 1
Joined: Tue Oct 10, 2023 5:24 am

Re: after upgrade to 5.11.2 only admin users can acknowledge alerts

Post by Kamay21 »

If you're experiencing a specific issue with Nagios XI after upgrading from version 5.11.1 to 5.11.2 where only admin users can acknowledge alerts, it's important to troubleshoot and identify the possible causes. geometry dash lite
shoreypu
Posts: 134
Joined: Wed Mar 13, 2019 2:06 pm

Re: after upgrade to 5.11.2 only admin users can acknowledge alerts

Post by shoreypu »

I found that only users with a contact name are authorized to acknowledge alerts as well. Do we know if this has been acknowledged as a a feature or a bug? We use mailing lists rather than directly sending alerts to users, so its a bit inconvenient to now have to add contacts for all our users.

John
swolf

Re: after upgrade to 5.11.2 only admin users can acknowledge alerts

Post by swolf »

Hi @shoreypu,

A couple of organizations have reported this issue to us, and we're currently looking into it. We don't think users should be required to have contact names, but it does look like that's the current functionality. We're sorry for any inconvenience this is causing. For the specific organization you're describing, I would recommend rolling back to 5.11.1 until this is resolved.

EDIT: it does look like we reverted the change for 5.11.3. Given this, either rolling back to 5.11.1 or upgrading to 5.11.3 should resolve your issue.
Post Reply