|Network Eagle Checks|
As an option, you can supplement a check in Network Eagle with dependencies between your various checks. The availability of a service can depend on the availability of another service. For example, if your HTTP server is behind a router, there is no use checking the HTTP server if the router is down. You can say that your HTTP server depends on the router. Also, you can define a dependency for another check.
Select the Dependencies page in the Edit Check dialog box . Here you can edit dependencies for the current check.
You can do the following in this dialog box:
Click the Add button to define a dependency(-ies). The following dialog box will open:
Select the check or the check group you want the currently edited check to depend on. Select one of the dependency conditions (read about them below in this article). If you select a check group, you can select the Apply group recursively check box to add all checks and subgroups in the selected group. If this check box is not selected, only checks in the selected group will be added as dependencies and no subgroups will be processed.
A dependency condition defines when checking is allowed. To understand what it means, please, take a look at the first picture above. In the picture we are editing a ping check. There are two dependencies defined. If the ping check in the picture is stopped, the dependencies make no sense. But if this check is started, before real pinging two additional dependency conditions should be true before pinging is started: