%Reply_Integer% is one step behind in "Use warning stat

[JuergenF]

Hi all,

I use %Reply_Integer% in the "Use warning status if" expression
(%Reply_Integer% > 500)

It's a HTTP test.

The status-switch to warning occurs in the test following the one that is slower than 500 ms. So it looks to me that %Reply_Integer% refers to the "last test result" instead of the "current test result" .

2012-12-22 05:30:46 Host is alive 9125 ms
2012-12-22 05:33:47 Warning 141 ms
2012-12-22 05:36:50 Host is alive 140 ms

2012-12-22 08:17:17 Host is alive 328 ms
2012-12-22 08:20:26 Host is alive 4844 ms
2012-12-22 08:23:29 Warning 281 ms
2012-12-22 08:26:31 Host is alive 344 ms

Can you please check that.
HM 9.30

Thanks

Juergen

[JuergenF]

Sorry


The following variables may be used in the expressions that define Normal and Warning statuses (see Optional status processing section of the manual).

%SuggestedReply_Integer%

[KS-Soft]

Yes, this is correct behavior.
Quote from the manual
--------------
IMPORTANT note: HostMonitor checks logical expressions after test check is done and "reverse alert" option is processed.
I.e.
- HostMonitor performs the test;
- processes "Reverse alert" option;
- sets "suggested" macro variables (%SuggestedStatus%, %SuggestedSimpleStatus%, %SuggestedReply%, %SuggestedRecurrences% and %FailureIteration%) without touching regular counters (%Status%, %Reply%, %Recurrences%, etc);
- then HostMonitor checks "Warning" and "Normal" expressions, processes "Tune up Reply" option and finally modifies current test status and statistisc counters (Status, Reply, Alive%, Passed tests, Failed tests, etc).
--------------

Regards
Alex