Skip to main content
Matrix42 Self-Service Help Center

Viewing the dependency map for objects


The Show Dependency Map action becomes available after you install the Infrastructure Forensics package from the Extension Gallery. Running this action opens a diagram that shows how the selected object is connected to other objects in the system. This is very useful when some kind of failure occurs and you need to check all related objects to discover the reason of the failure or manage the consequences.

This feature is an enhancement of the standard Show Dependencies action.

The Infrastructure Forensics package can be installed on Matrix42 Enterprise Service Management systems starting from version 10.1.

The scope of dependency mapping

You can execute the Show Dependency Map action for the following types of objects:

  • Services, service bundles, service groups, and service sets in the Service Catalog app;
  • Incidents in the Service Desk app;
  • Computers, monitors, printers, portable storage devices, general peripherals, SIM cards, universal assets, and network devices in the Assets app;
  • Custom configuration items.

Limitations of the current implementation

Viewing the dependency map is not possible for the following cases:

  • Entity does not have a state value in the SPSCommonClassBase data definition.
  • Entity is a simple CI.
  • Entity does not contain the SPSCommonClassBase data definition.


After you install the Infrastructure Forensics package, the Dependency Map Settings navigation item becomes available in the Master Data application. Open this dialog for editing to set up which dependencies should be tracked.

On the Mappings tab of the dialog, there are two settings with default values:

  • Allowed Configuration Items for Object Class Dependency. By default this settings contains a list of all objects for which dependencies can be set on the Dependencies tab of the dialog. You can exclude an object if dependency mapping should not consider it.
  • Dependency Attribute Mapping. This a list of all relations between configuration items that are tracked by the dependency mapping. You can add relations to this grid.

On the Display tab of the dialog, you can adjust the visual display of configuration items on the dependency map:

  1. In the Configuration Item field, select an object.
  2. Now you can set a specific icon for this object in the Icon field.
  3. In the Display Expression field, you can set a display expression that will be used to label this object on the dependency map.


Adding custom configuration items to the dependency mapping

To enable the dependency mapping for custom CIs, the relation between them needs to be set up from both sides.


You have a custom configuration item Business Application with data definition TSTBusinessApplicationClassBase which has an attribute and a relation:

  • Attribute: Name
  • Relation: Host (n:m to SPSComputerClassBase) 

If you want to include the business application to the dependency map for computers, you need to set up two relations:

  • Relation starting from the Computer configuration item
  • Relation starting from the Business Application configuration item

How the dependency mapping works

When you run the Show Dependency Map action for a selected object, a wizard opens. It displays a diagram of relations between the selected record and other records that are eligible for dependency tracking.

The Show Dependency Map action is available in the actions menu and on the Dependencies tab of a dialog.

Right-click on any item to open the context menu where you can select one of the 5 layouts:

  1. Standard. The default layout distributes items evenly across the chart and uses links of a consistent length.
  2. Organic. Multiple components are grouped into circular arrangements with larger components in the center.
  3. Sequential. It is a display of a clear parent-child relationship between elements to convey a level of each element.
  4. Lens. Highly-connected items are put in the center while the less connected ones pushed into the periphery.
  5. Structural. The layout puts items with similar attributes together in fans.


  • Was this article helpful?