Nagios Support Forum

Anyone else using the ServiceNow NagiosXI connector to cut tickets for NagiosXI events?

We don't use notifications (email/paging) from NagiosXI. Our ServiceNow instance uses a NagiosXI connector which generates an incident ticket for any NagiosXI critical events. This works fine, but we want a way to suppress ticketing for scheduled downtimes.

It looks like the NagiosXI schedule downtime function suppresses notifications, but it does not seem to prevent events from being generated so ServiceNow still cuts tickets. I could use core-config to make the host(s)/service(s) inactive but that's pretty cumbersome. Options for scheduled suppression of the ticketing?

Thanks,

Dave

I think the challenge with that connector might be that it polls XI for state (by default every two minutes), which ignores the Nagios secret sauce.

Nagios keeps monitoring the hosts during downtime, and keeps track of state. The key thing about scheduled downtime is that it suspends notifications.

The SNow connector does not seem to take schedule downtime into account. When the SNow connector keeps polling every two minutes, it probably responds to any state change however it is set up to do.

Instead of SNow polling XI, I would use the notification command to send an API call to SNow. You can use macros to send all the information you want/need. This way when you are in downtime, the host will not send the notification.