Login
Dependency Rules
The main purpose of setting dependencies is to avoid unnecessary alerts for targets when they depend on each other.
For example: if you monitor a router and a web server that is connected through this router, and the router fails, it's clear that the web server will be inaccessible which is equal to a failure. In this case, you can create a rule that no alert is sent for the web server if your router is failing at the same time. If this rule is in place, each time the system detects an error with your web server, it will check the status of your router, and if the router is failing, no alert will be sent for the web server. You will be notified for the error of the router and obviously all systems behind this router will be unreachable.
To define a dependency rule for a target you should configure the following parameters:
Alert type - select the alert type that will trigger the new dependency rule. This allows you to create rules that apply to specific error types or target recovery.
Targets - select the targets on which the monitored target depends. You can select a specific target or target class, and if a target class is selected you should define the host(s) where the targets in this class are located.
Targets host - select a host where the targets on which the current target depends are located.
Status - what should be the status of the targets, on which the current target depends.
Action - select the action that will be performed if the rule has been satisfied. Currently you can select between 3 options - to block the alert messages, to send a dependency satisfied message or to take no action.
Similar topics
Knowledge base
Howtos
Glossary
Frequently asked questions
