We get a lot of Unknown's through out the day - the vast majority being from snmp get tests and performance counter tests. Since snmp is udp, if the packet gets lost in transit, HM reports it as an 'Unknown' status. We also get dozens of Unknowns each day from performance counter based tests (using the local RMA agent on the server) which results in various reply's - (RMA: 301 - Error: A counter with a negative value ..., Inaccessible Value, RMA: Cannot read data, etc.) which all clear up after another retest or two.
Is there a way to use the new variables (to set normal or warning) to return a 'normal' or 'warning' if the snmp packet is lost in transit for 3 samples in a row, or if a performance counter (or an RMA agent request to get perf counter data) fails to respond with a value 3 times in a row?
Thank you
Handling 'Unknown' status with new status codes
Why not? Have you tried expression like ('%SuggestedSimpleStatus%'=='UNKNOWN') and (%CurrentStatusIteration%<3) ?Is there a way to use the new variables (to set normal or warning) to return a 'normal' or 'warning' if the snmp packet is lost in transit for 3 samples in a row, or if a performance counter (or an RMA agent request to get perf counter data) fails to respond with a value 3 times in a row?
Do not forget to disable "Treat Unknown as Bad" option.
On the other hand, do you really need to replace Unknown status? It does not start alerts (if "Treat Unknown as Bad" option is disabled) and does not increments "bad" statistic counters.
Try to increase timeout specified for this agent.RMA: Cannot read data, etc.)
BTW: We recommend to use WMI test instead of Performance Counter. WMI works more reliable.
Regards
Alex