I believe I’m seeing the same issue, myself. When attempting to trigger a UNIX shell script from the alert exec for threads that go out of UP proto status for longer than 30 minutes, the engine triggers the same exec sequence twice. So instead of receiving ONE alert email kicked off by the shell script, we’re getting two.
Here’s what my alert looks like:
{VALUE pstat} {SOURCE {test_thread_in}} {MODE actual} {WITH -2} {COMP {!= up}} {FOR once} {WINDOW {* * * * * *}} {HOST {}} {ACTION {{exec {emailAlert.sh [Facility] [IP_Address] [Site] “%A” dummy@email.com}}}}
This doesn’t happen when it’s setup to trigger against queue depth, but it does when I set it against proto or engine status.
I’ve spun my wheels on this for hours, and can’t seem to find the silver bullet to slay the beast. Any assistance on this would be greatly, greatly appreciated.
Thanks in advance!