In this instance I am looking at CPU Usage. If the test is unlucky and tests during a CPU burst it will return 100% usage which then marks the test as bad. What I'd like to do in an ideal world (for any test)
Test comes back as over 70% - Test stays as OK but wait for 60 seconds
Test comes back on second run as 70% - Test stays as OK but wait for 60 seconds
Test comes back on third run as 70% - Test marked as bad and action generated.
Any way I can do this?
Is there any way to delay a test then run it again
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
You may use "Use Normal status" option with expression like the following:
('%SuggestedSimpleStatus%'=='DOWN') AND (%FailureIteration%<3)
This option is located on the bottom of Test properties dialog (Optional status processing section)
Please check for details at:
http://www.ks-soft.net/hostmon.eng/mfra ... rmalstatus
('%SuggestedSimpleStatus%'=='DOWN') AND (%FailureIteration%<3)
This option is located on the bottom of Test properties dialog (Optional status processing section)
Please check for details at:
http://www.ks-soft.net/hostmon.eng/mfra ... rmalstatus