Slack notifications do not respect recurring or scheduled do

[distracted24x7]

Nagios XI versioon 5.7.5 with working Slack integration

Problem: Slack notifications do not respect recurring or scheduled downtime.

Nagios XI is listening to recurring downtime and not sending me text messages or email about the services I have told is not to bother me with. We have several machines that normally report high CPU levels over the course of a day. The problem is two fold. One, Nagios XI only reports those problems, with a rare exception, to Slack. That may be my fault. Second, Slack even gets and posts the alerts I have told Nagios not to tell me about. Those services about high CPU just keep coming through Slack. I don't know why that is and am hoping you can help me figure it out.

[benjaminsmith]

Hi @distracted24x7,

Welcome to the Nagios Support Forum! And thank you for using Nagios XI.

First, just want to confirm how the Slack integration was setup, did you follow the guide below or another procedure?

Integrating Slack With Nagios XI

Looking over the issues described, the first issue sounds like the Slack contact maybe the only contact assigned for this service. You can check this in the CCM by going to Configure > CCM > Monitoring > Service then find the specific service and click on the Alert Tab. Then verify the contact settings by clicking the Manage Contacts button.

On the second issue, there is a distinction between alerts and notification in Nagios XI. You may be getting alerts in the GUI but it shouldn't send out notifications (i.e. execute the slack notification handler). If you're getting notifications, can you verify that they are not the start and stop downtime notifications ( these can be turned off in the configuration).

Please send PM the system profile and the exact name of the service and I can double-check the configuration settings for you.

To send us your system profile.
Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button

Best Regards,
Benjamin

[distracted24x7]

Thanks for getting back to me. I followed the instructions you posted setting up slack integrations.

I am getting notifications about service issues I specifically told Nagios not to bother me with. I don't see the start or stop downtime notifications.

Slack is one member of a group of users who are supposed to receive notifications. I believe it is all setup properly. Please let me know if you find something isn't right.

Most of the services I have problems with are called 'NCPA: CPU Usage'. The other is 'VinBasic: File presence and Status on FTP' and 'NCPA: CPU Usage for OEM Scanner Instances'

[benjaminsmith]

Hi @distracted24x7,

Thanks for the profile. Those hosts and services have the slack_service_notification_handler set as the Event Handler, and that's why you are getting extra messages. Event handlers operate differently than notification handlers and are commonly used to reset or reboot a host or service experiencing an issue.

Just remove this command from the event hander settings in the Check Settings tab in the Core Configuration Manager. Since the Slack contact is already a member of the contact group assigned you will get a notification via Slack .

Hope that helps, and let us know if you get it resolved.

Reference:
Using The Core Config Manager For Host Management

[distracted24x7]

Morning,

I reconfigured the event handler for service notifications to xi_service_notification and the problems are gone. That was some bad advice from somewhere on the internet. Anyway, thank you very much for your help and education on the proper way to think about event handlers. I don't miss clearing all those alerts every morning and a solid night's sleep... Thank you!

[benjaminsmith]

HI @distracted24x7,

Your welcome! Glad that's working for you now.

We'll go ahead and mark this as resolved. Feel free to open another post if you have any new questions.

--Benjamin