Relaties visualiseren
Explore component graph · Explore location graph · Review relationship walk
Voor wie
Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.
Taken
Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.
Explore component graph
Explore component graph.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- A visualization is only as complete as the underlying relationships; empty graphs usually indicate missing links, filters, or unavailable permissions.
- Relationship categories such as hierarchical, service, responsibility, technical, and structural can be toggled to reduce clutter.
- Moving or adding components may update operational CMDB relationships, so users should understand the intended location or dependency before saving.
- Access-group links come from recorded relationships; do not infer permission from a graph alone.
- Open Assets → Visual Inspection → Components.
- Search for the component, building, floor, room, or other object to inspect.
- Use filters to include the relationship categories relevant to the question.
- Navigate from one node or location level to another to follow dependencies or placement.
- Inspect missing expected relationships as possible CMDB data quality gaps.
- When supported, add or move components from the visualizer only after confirming the intended structure.
Expected outcome: The user has reviewed the result of explore component graph in the application.
Explore location graph
Explore location graph.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- A visualization is only as complete as the underlying relationships; empty graphs usually indicate missing links, filters, or unavailable permissions.
- Location visualization focuses on hierarchy and placement, while component visualization focuses on relationships around a selected component.
- Relationship categories such as hierarchical, service, responsibility, technical, and structural can be toggled to reduce clutter.
- Moving or adding components may update operational CMDB relationships, so users should understand the intended location or dependency before saving.
- Open Assets → Visual Inspection → Locations.
- Search for the component, building, floor, room, or other object to inspect.
- Use filters to include the relationship categories relevant to the question.
- Navigate from one node or location level to another to follow dependencies or placement.
- Inspect missing expected relationships as possible CMDB data quality gaps.
- When supported, add or move components from the visualizer only after confirming the intended structure.
Expected outcome: The user has reviewed the result of explore location graph in the application.
Review relationship walk
Review relationship walk.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- A visualization is only as complete as the underlying relationships; empty graphs usually indicate missing links, filters, or unavailable permissions.
- Location visualization focuses on hierarchy and placement, while component visualization focuses on relationships around a selected component.
- Relationship categories such as hierarchical, service, responsibility, technical, and structural can be toggled to reduce clutter.
- Follow each recorded link in its own direction; a multi-step path does not imply an unrecorded direct relationship.
- Open Assets → Visual Inspection and choose the Components or Locations view.
- Search for the component, building, floor, room, or other object to inspect.
- Use filters to include the relationship categories relevant to the question.
- Navigate from one node or location level to another to follow dependencies or placement.
- Inspect missing expected relationships as possible CMDB data quality gaps.
Expected outcome: The user has reviewed the result of review relationship walk in the application.
Aanbevolen werkwijze
- Geef voorrang aan gegevens die dienstverlening, compliance en kosten beïnvloeden.
- Leg relaties vast die een concrete operationele vraag beantwoorden.
Gerelateerde handleidingen
Lees verder in Assets en CMDB
Registraties, relaties, groepen, documenten en CMDB-structuur.