Service dependencies

Service dependencies maps let you visualize the relationships between the business, technical, and external services defined in your Service Catalog. You can access the dependencies map for a service to view that service's direct dependencies and explore how that service relates to other services in your architecture. You can also access the dependencies map for an incident to view which services are impacted, investigate which other services may be affected, and to identify potential root causes.

The direction of arrows on the map indicates what a service depends on. For example, in the image above, 'Service A' depends on 'Service B' and 'Service C' (and conversely, 'Service A' is depended on by 'Service 1' and 'Service 2'). You can use the dependencies map to manually define the dependencies between your services.

The icon for each service lets you see at a glance if the service is impacted by any active incidents, and the highest severity level of those incidents. While the map displays a focused view by default, you can expand the map to view additional upstream and downstream services. The icon to indicate if a branch of the map can be extended is color-coded by the highest severity of any active incidents impacting services in the hidden branch.

The following sections describe the actions you can perform on the service dependencies map: