Could I request an additional feature as well as the 'treat unknown as bad'.
This would be "ignore unknown results", or "treat unknown as last result".
ie. If the test was previously bad & now returns unknown I don't want the status to change. Ditto if the test was previously good.
Basically for some tests I don't ever want to be alerted if the status is unknown. Only if it's definately changed to bad or good.
Ignore 'unknown' status
You want such behaviour for most of your tests? Or just some?
You may use "advanced" mode action to start alerts on "bad" or "good" statuses only. E.g. you may use expression like ('%SimpleStatus%'=='DOWN') and (%Recurrences%==1) for bad actions, or ('%Status%'=='Bad Contents') and (%Recurrences%==1)
Regards
Alex
You may use "advanced" mode action to start alerts on "bad" or "good" statuses only. E.g. you may use expression like ('%SimpleStatus%'=='DOWN') and (%Recurrences%==1) for bad actions, or ('%Status%'=='Bad Contents') and (%Recurrences%==1)
Regards
Alex
I only want to use it on some tests, but would be nice to have it as a standard option.
Your reply also doesn't work as a work-around, let me try to explain:
I already have alerts that start on just "bad" or "good" status, only alerting me with a repeat count of 1.
The problem seems to be that with unknown events, the next bad or good event believes it's the first occurance, triggering the alert.
So I have an item that's flagged "good", then I get an "unknown", and then another "good". I get a message saying it's changed to good when really nothing's happened.
What I want is for the system to ignore that "unknown" log in the middle. Ideally ignore it completely, but a useful workaround would be to flag that unknown event as being the same as the previous (good in this case). Ok, it'll add an extra item to the count, but it will stop unnecessary alerts.
Your reply also doesn't work as a work-around, let me try to explain:
I already have alerts that start on just "bad" or "good" status, only alerting me with a repeat count of 1.
The problem seems to be that with unknown events, the next bad or good event believes it's the first occurance, triggering the alert.
So I have an item that's flagged "good", then I get an "unknown", and then another "good". I get a message saying it's changed to good when really nothing's happened.
What I want is for the system to ignore that "unknown" log in the middle. Ideally ignore it completely, but a useful workaround would be to flag that unknown event as being the same as the previous (good in this case). Ok, it'll add an extra item to the count, but it will stop unnecessary alerts.