Relations

Relations describe how assets connect (e.g., VM ↔ host, user ↔ group, disk ↔ machine). They are discovered automatically; no manual maintenance required.

• Bidirectional: every relation is viewable from both sides.
• Derived from discovery data and stitching/identity rules; updated each discovery run.
• Computed/read-only for users; you cannot not manually manage relations between assets.
• Essential for Governance, impact analysis, relation-based tags.
• History: changes in relations are reflect after discoveries; You can explore and understand changes to relations using history

Tip

When filtering tables, use relations to hop between asset types (e.g., show VMs where Host = X).

Examples:

• VM → is hosted on → Host
• Host → is hosting → VM
• User Account → is member of → Group
• Group → has member → User
• Machine → Has primary user → User
• User → is primary user for → Machine

Use cases

• Relation-based filters in tables (e.g., “VMs where Host = X”, “What department is laptop connected to via its owner?”).
• Relation-based tags (e.g., VM inherits Cluster name via Host).
• Service mapping/impact analysis by traversing dependency links.