Just my $.02, but I would make a second DURATION type counter that gets reset on every state change and add a keyword called something like LASTCHANGE. That way the user can decide how he wants to handle duration type rules. Some users may want rules based on the last time a test was "green" and other rules based on the last time the state changed.
Henrik Stoerner wrote:
In <BAY130-F27256BE7B86074DCCF21E3BADC0 at phx.gbl> "Patrick Vaughan" <patrick_a_vaughan at hotmail.com> writes:
I need to send an Email if a test is yellow, and escalating pages if it is red. My problem is that a test went yellow over the weekend when nobody was checking Email, then in the middle of the night went to red. Which caused techs, backup techs, managers, and the CEO to be paged because the duration was over 24 hours.
Is there any way to reset the duration counter when the state changes. Instead of just when the state changes from green?
No.
The problem with this is that you'll get tons of alerts if a status is wobbling just around the red threshold.
I do understand your predicament with the current way alerting works, but right now I haven't found the optimum way of doing it.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk