Dependency Concept

Dependencies can be selected for groups, servers and sensors (to pause monitoring) as well as for notifications (to mute notification messages).

Choosing dependencies should be done with great caution as it can completely knock out your monitoring if not used correctly!

Here are some tips:

·      Sensors used a dependency should be very simple sensors (e.g. PINGs) with short intervalls (much shorter than the dependent sensors) and with short timeouts.

·      To monitor the availability of leased lines monitoring the first hop behind the line is a good idea. Use the “tracert” command to find out the IP of this first hop.

·      Make sure you set reliable notifications for the sensors that you will use as dependency so you will be notified about the fact that IPCheck can’t monitor your other sensors!

·      You must make sure that you do not configure loops into your dependencies by making two groups/servers/sensors dependent on each other, then both sensors will never be “unpaused”.

·      Dependencies can be cascaded