Master test ... vicious circle

[Igorek]

There is a ping-test as the master-test and URL-request dependent on it. Parameters of the ping-test are set by "Timeout 4000, Packet size 0, Packets 4, Status is bad when 100 % of packets of lost". Parameters of URL-request are set by default.
There was a following situation. The ping-test has the status "Bad", because timeout is 5000. Throughput of a network suffices that the URL-request had the status "Alive", but it is not executed, as " Wait for Master ". There is one alarm. I solve a problem to increase throughput of a network, but I do not know, whether is accessible URL. If the web-server will fall, I do not get to know about this, yet I shall not check up manually.
Let I do URL-request independent of the ping-test. I get in a situation, at full absence of a network, that the ping-test and URL-request both have the status "Bad", hence there are two alarms. But in fact it is incorrect. My web-server is alive, but it is inaccessible because of bad connection. Hence it is necessary to do URL-request dependent on the ping-test.
We receive a vicious circle...

[KS-Soft]

Sorry, I do not understand what the problem is.
If you want ping test to fail when network completely inaccessible, increase timeout and number of packets.
If you want ping test to fail when network a little busy, keep your settings.

What exactly do you need? One alert when network is slow, another alert when network is down, and 3rd alert if just web server does not respond?
Then I think you should setup 2 ping tests with different parameters. And use "NetIsDead" ping test as master test for another "NetIsSlow" ping test and for both URL tests.

Regards
Alex

[Igorek]

Then I think you should setup 2 ping tests with different parameters. And use "NetIsDead" ping test as master test for another "NetIsSlow" ping test and for both URL tests.

Thanks for the answer. It is the decision of a problem.
I too have late thought of such decision. I have not had time to write on a forum.