DocumentaciónHelp

Accept or dismiss proposed relationships

Review the dependencies ARGUNIS learned by seeing items go down together and in order, and accept them for incident correlation.

On this page

When two items go down together and in order several times, ARGUNIS proposes that one depends on the other. An accepted proposal counts for incident correlation like any inventory relationship: the next time they go down, one will be the probable cause and the other an affected incident.

Before you start

  • To accept, dismiss, or recalculate, you need Administer in Core (Administrator role or a company role with that level).

  • Learned correlation must be turned on (see Dependency correlation). If it's turned off, the page tells you.

Steps

  1. Go to Core → Proposed relationships.

  2. In Status, leave Pending.

  3. In each row, review:

    • Depends on → needs: the two items and the relationship type ("runs on" or "depends on"), with the reason and examples.

    • Support: how many times they went down together, how many outages each one had, and how long after the second one went down.

    • Confidence: the percentage of times one's outage came with the other's.

    • Last: the last time they went down together.

  4. Click Accept to create the relationship, or Dismiss so it isn't proposed again.

  5. If you dismiss, you can write a Reason (for example, "they go down together due to the same backup window") and confirm with Dismiss.

Recalculate now recalculates on the spot the dependencies by connections, by DNS, and the proposals, without waiting for the next run.

What happens next

  • Accepted ones appear in Accepted and in the Relationships section of each item's detail page.

  • Dismissed ones stay in Dismissed with who decided them.

  • If someone else already decided on a proposal, you'll see a message and the view refreshes.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close