Hello,
We've got a bit of a mystery on our hands involving notification.
Here's the setup:
We're trying to send critical alerts, and only critical alerts, to Service Desk -- we don't care about WARNS or OKs, we just want critical alerts.
We've written an event handler for both services and hosts which sends the alerts to SD and it works fine.
The problem is, we're getting ALL messages in SD, not just critical alerts. It gets weird from here.
We have a user and the user's ALERT settings are set to only alert on either critical service alerts, or host down. The notification command for this user is the SD handler. This user is set as a managed contact on all hosts and services.
So if I'm understanding the workflow correctly, the only notifications we should be seeing in SD are critical service alerts and/or host down, but that's not how it's working: we get everything, as I've said before.
Here's where it gets strange.
If I add a new host/service and assign the aforementioned user as a managed contact, it works -- we only see critical alerts in SD. I've looked and looked at the new service and an old service side-by-side, but I can't see any difference. I'm banging my head on my desk trying to figure this out.
Any idea where to look or what I might be doing wrong?
Thanks for any rendered help,
-- Mike Beebe
A notification mystery
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: A notification mystery
Do you have an event handler attached to the hosts/services in addition to notifications?mbeebe wrote:We've written an event handler for both services and hosts which sends the alerts to SD and it works fine.
Re: A notification mystery
Hi Scott,scottwilkerson wrote:Do you have an event handler attached to the hosts/services in addition to notifications?mbeebe wrote:We've written an event handler for both services and hosts which sends the alerts to SD and it works fine.
We do not.
-- Mike
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: A notification mystery
Can you send me a System Profile from Admin -> System Profile along with the name of this contact/User as well as the one host/service that is working correctly and one that is not?
Re: A notification mystery
Scott,scottwilkerson wrote:Can you send me a System Profile from Admin -> System Profile along with the name of this contact/User as well as the one host/service that is working correctly and one that is not?
Will do.
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: A notification mystery
Hi @mbeebe,
Once you PM the profile, please reply to this thread again to bring up in the queue. Thanks.
Once you PM the profile, please reply to this thread again to bring up in the queue. Thanks.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: A notification mystery
Bumping this thread; PM sent to Benjamin (by mistake)
Re: A notification mystery
Hi,
Sorry about this, but we solved the mystery: another account had the same event handler tied to it and it was taking precidence in the alerting order. We removed the event handler from that account and things are functioning as expected now.
Please close this ticket and thank you for all your help.
-- Mike Beebe
Sorry about this, but we solved the mystery: another account had the same event handler tied to it and it was taking precidence in the alerting order. We removed the event handler from that account and things are functioning as expected now.
Please close this ticket and thank you for all your help.
-- Mike Beebe
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: A notification mystery
Glad to hear this is sorted out!mbeebe wrote:Hi,
Sorry about this, but we solved the mystery: another account had the same event handler tied to it and it was taking precidence in the alerting order. We removed the event handler from that account and things are functioning as expected now.
Please close this ticket and thank you for all your help.
-- Mike Beebe
Locking thread