Re-fire trigger when trigger PROBLEM state changes
Hello
I have an item configured to get the number of RAID hotspares available on a system. I'm trying to configure a trigger that will be tied to an action that sends an email.
I am trying to achieve a trigger that fires once when the number of hotspares drops below two. It should fire again if the number of hotspares changes.
I've tried various things with trigger hystersis and multiple event generation (which thinking about it now was obviously not the way to do it).
My example use case is:
a)
- host has 2 hotspares (OK state)
- 1 hotspare is used for a rebuild: the trigger should fire once
- a new hotspare is brought online: trigger should go to OK state
b)
- host has 2 hotspares (OK state)
- 1 hotspare is used for a rebuild: the trigger should fire once
- the last hotspare is used for a rebuild: the trigger should once more
- additional hotspares are brought online: I'm open to whether or not the trigger should fire once more to reflect the change
Is this achievable? Right now having two distinct triggers for "1 hotspare available" and "no hotspares available" works but is not ideal (or very scalable).
Thanks, Lewis
I have an item configured to get the number of RAID hotspares available on a system. I'm trying to configure a trigger that will be tied to an action that sends an email.
I am trying to achieve a trigger that fires once when the number of hotspares drops below two. It should fire again if the number of hotspares changes.
I've tried various things with trigger hystersis and multiple event generation (which thinking about it now was obviously not the way to do it).
My example use case is:
a)
- host has 2 hotspares (OK state)
- 1 hotspare is used for a rebuild: the trigger should fire once
- a new hotspare is brought online: trigger should go to OK state
b)
- host has 2 hotspares (OK state)
- 1 hotspare is used for a rebuild: the trigger should fire once
- the last hotspare is used for a rebuild: the trigger should once more
- additional hotspares are brought online: I'm open to whether or not the trigger should fire once more to reflect the change
Is this achievable? Right now having two distinct triggers for "1 hotspare available" and "no hotspares available" works but is not ideal (or very scalable).
Thanks, Lewis