Managing Dependencies

Using “dependencies” you can pause the monitoring of sensors or the sending of notifications based on the status of another sensor to avoid false alarms and incorrect recording of downtimes.

If you – for example – monitor servers over a leased line then it makes no sense to send monitoring requests to the servers if the leased line is down since IPCheck can’t even reach the servers. The idea is to monitor the availability of the leased line and then pause monitoring of the servers if the leased line is not available at all.

In our example you would set up a short-intervalled PING sensor to monitor the first hop behind the leased line. Then select this sensor as dependency for the sensors that monitor servers behind the leased line.

This way you will not be notified of server downtimes if actually the leased line goes down, also no downtime will be recorded for the servers’ sensors.

More:

Dependency Concept

Dependency Example

Using Tracert to Find Out Hop IP Addresses

Group, Server and Sensor Dependencies

Notification Dependencies

Admin Dependencies