Dependency correlation
Turn on and tune how ARGUNIS groups related outages, discovers dependencies, and learns new relationships.
On this page
When related items go down within a time window, the incident of the lowest one in the chain becomes the probable cause and the rest become affected items, even if they're in different groups. The notification goes out for the cause and the affected items go in the same notification. Without relationships, grouping is by inventory group.
Before you start
Anyone can see the setting. To change it you need Administer on Core (Administrator role or a company role with that level).
Steps
Go to Core → Alarm policies.
Scroll down to Dependency correlation.
Adjust each block:
Correlation: check Enabled and set the Window (minutes), from 1 to 60.
Discovery by connections: with Enabled, ARGUNIS creates automatic "depends on" relationships from what the agents report (listening ports and outgoing connections). Set after how many days a relationship becomes "No traffic" (it stops counting for correlation) and after how many it is retired (deleted). Requires recent agents.
WebService/TCP DNS: with Enabled, ARGUNIS resolves the name of each WebService and TCP and links it to the inventory server that has that IP.
Learned correlation: with Enabled, ARGUNIS proposes relationships when two items go down together and in order. Set the History (days), the Window (minutes), the Minimum times, and the Minimum confidence (%).
Click Save. To undo, click Discard changes.
What happens next
New incidents are grouped using the chosen window.
Discovered relationships appear in the Relationships section of each item's details, marked "by connections" or "by DNS". An administrator can Hide an automatic relationship so it doesn't count.
Learned relationships wait for review in Accept or dismiss proposed relationships.