At the moment I can trigger action after n consecutive bad tests.
n is usually set to >= 2 to avoid alarms/actions caused by single events
But when e.g. a test is bad once every ten times it will never trigger an action.
WISH: An additional Condition to start action based on an additional "bad result counter"
Start action when at least n "bad" results occur within m tests.
Reset the counter when less than x "bad" results occur within y tests
This could also solve the problem mentioned in [url]http://www.ks-soft.net/cgi-bin/phpBB/vi ... php?t=2843[/url]
Thanks a lot
Thomas
action when test is instable
-
- Posts: 166
- Joined: Sat Apr 15, 2006 2:14 pm
- Location: Germany, Bavaria
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact: