Ad Widget

Collapse

Trigger Sends Extra Messages On State Change

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • craigmbailey
    Junior Member
    • Jul 2009
    • 5

    #1

    Trigger Sends Extra Messages On State Change

    I have a trigger setup that include a time interval which works fine. However if the trigger is in warning state (which I get emails on) then the timeframe hots where it is the exception I get a recovery message. Then at the end of the timeframe I get another email saying it is in warning again. Anyone know how to eliminate this? It seems as the trigger is going to a good state when the time frame hots then back to its warning state after. Thanks in advance.

    Trigger:
    ({prod:grpsum["Production","h.active[]","last","0"].last(0)}<9) & (({prod:grpsum["Production","h.active[]","last","0"].time(0)}<031400) | ({prod:grpsum["Production","h.active[]","last","0"].time(0)}>033500))

    If it is in warning before 03:14 here is what happens.
    1) At 03:14 I get a Recovery message for the trigger.
    2) At 03:35 I get a Warning email saying it is back in a warning state again.

    I want the warning email but I do not want the trigger sending out both of these extra emails before and after the excluded timeframe. Anyone know a way around this?
  • globifrosch
    Member
    • Sep 2005
    • 74

    #2
    Originally posted by craigmbailey

    If it is in warning before 03:14 here is what happens.
    1) At 03:14 I get a Recovery message for the trigger.
    2) At 03:35 I get a Warning email saying it is back in a warning state again.
    IHMO this is the way this works.

    Comment

    • craigmbailey
      Junior Member
      • Jul 2009
      • 5

      #3
      So I guess the best way to get around this is to make a flexible interval for 3:14-3:35 and make the update set to 1260 which would be the whole timeframe between those times and then remove the time variables from the trigger. This would then cause the trigger to not go back to a "OK" state then back to a "WARNING" as it originally was before the 3:14 time period.... Anyone else have any insights?

      Comment

      Working...