![]() |
![]() |
Subject: | Event trigger/notification not firing |
Author: | Daniel Rich |
Posted: | 2016-02-09 15:54 |
So I have quite a few trigger/notification pairs in my system and for the most part they all work. However, I have a new one that I just can't get to fire. The idea is that when a clear event comes in it will update any open incidents in our ticketing system for that particular device/component combination. The script to do that is done and tested, but the trigger/notification that should be running it isn't working and nothing shows up in zenactiond.log.
The trigger (clear_to_ticket) is enabled and is pretty basic:
The notification (update_ticket_on_clear) has the above trigger mapped to it, is enabled, has the 'Send Clear' checkbox checked and is set to run the following command (for both the regular command and clear command):
However, it never runs when a clear event comes in. In fact, the only thing i can find in zenactiond are lines like:
2016-01-29 09:45:48,455 DEBUG zen.notifications: Notification is enabled: update_ticket_on_clear
2016-01-29 09:45:48,455 DEBUG zen.notificationdao: Notification "" does not subscribe to this signal.
Does anyone have any ideas where to look for what might be going on Setting zenactiond into debug mode didn't help, I didn't find any more information in the logs.
I realize I could also do this from a transform, but since the ticket update can block I though a notification would be a better option.
Subject: | I found something interesting |
Author: | Daniel Rich |
Posted: | 2016-02-09 16:47 |
I found something interesting in debugging this problem... If I removed "Severity == Clear" from the trigger, I see the notification execute in zenactiond.log on both the critical and clear events. I also changed my Clear Command in the notification to just echo the severity. In the logs I see:
2016-02-09 14:45:35,617 INFO zen.actions: Command update_ticket_on_clear finished successfully (exit code 0) with the following output: Clearing event, severity: 4
So it looks like Zenoss is setting the severity to the value of the event being cleared, not "Clear"!
< |
Previous zenoss curl get manage ip |
Next Needed more forum features |
> |