Setting up component dependencies
The hierarchical arrangement Infrastructure > Components > Monitors helps avoid notification “spam” in the event that several components fail simultaneously.
For this purpose, the dependencies should be set on your infrastructure components:
- Connect components using the Link and Unlink tools on the Infrastructure page.
- Create meaningful and logical dependencies between components with the top-level component (e.g., router), the middle one being next (e.g., server), and the bottom one being the lowest-level component (e.g., Apache Server).
In real life, if a server goes down, the database goes down as well. If router stops working, too, then all network resources are unavailable. Hence, the above arrangement reflects a real-life situation.
When components are linked and an incident happens,Anturis sends out only one notification stating “Incident involving Router … STARTED” (see “Notifications”).
Such impact dependencies make sense only if hardware and software components are logically connected in real life. If not, don’t force-link the components. Just leave them as unlinked.
With an unlinked infrastructure, if several independent components fail simultaneously, the corresponding number of problems are generated and a corresponding number of notifications are sent.
Customer support service by UserEcho
