Page 1 of 1

Re-sending NagiosXI alert after Apply configuration.

Posted: Mon Feb 19, 2018 4:25 am
by Gonela
Hi Team,

NagiosXI Server integrated with Service Now. Every thing working fine with Snow but we are facing following issue.

Server 1 and Server 2 configured and integrated with SNOW.

Server1 having two services a and b ( status critical)

Server 2 having two services c and d ( status critical)

Issue : when ever b and d services goes down to critical and it is generating alert in snow at every 10min. because this alert , duplication occurring in snow incident for same service . for this reason we changed 10min to 0min time notification interval. Upto now this is working fine. When ever we applying configuration in core configure manager. again NagiosXI generating notification alerts.

Could you please stop regeneration of notification in NagiosXI after apply configuration in core configure manager

Re: Re-sending NagiosXI alert after Apply configuration.

Posted: Mon Feb 19, 2018 4:05 pm
by tgriep
It sounds like the default settings for the Sticky Acknowledgement was reset on the server.
Go to the Admin > System Settings menu and verify that the Sticky Acknowledgement is checked so when the system is restarted after an Apply Config, it will not resend the email notification.

Re: Re-sending NagiosXI alert after Apply configuration.

Posted: Mon Feb 19, 2018 8:32 pm
by Gonela
Hello tgriep,

Thanks for update.

Please find attached snap shot of my NagiosXI system settings.

If anything wrong , let me know

Re: Re-sending NagiosXI alert after Apply configuration.

Posted: Tue Feb 20, 2018 11:01 am
by tgriep
The Stick Acknowledgement is set correctly on your system. It is supposed to stop the notifications from being sent until the state changes and it should survive a restart of the Nagios process and not send another notification.

If you go to the Home menu and under the Incident Management > Acknowledgements menu, do you see that the service is Acknowledged?
Is this the only service that exhibits this issue or are there others?

Can you open up the status.dat file on the server, find that service and post the current settings so we can view them?