Service Dependencies

Adding service dependencies to respective services can help establish the network of relationships across your Service Catalog. Anytime a service is impacted by an incident, you can quickly discover dependencies to accurately understand the scope of impact from an incident. This can allow you to pull in all needed responding teams to quickly resolve the incident.

Create a Service Dependency

In the left nav, click Service Catalog followed by clicking Services. Once you select a specific service, you'll be able to navigate to the Service Dependencies tab inside your service.

From here you will have the ability to create a Downstream or Upstream dependency for the service you are visiting.

  • Downstream Dependencies: These services rely on the selected service being viewed.
  • Upstream Dependencies: The selected service being viewed relies on these other services.

Each dependency can be given a Dependency Note. This allows you to provide further context around the dependency relationship in the time of an incident or further discovery.

Each dependency highlights if the service is impacted, the dependency note, and owning team.


Update or Delete a Service Dependency

To update or delete a service dependency, click under the actions column next to the service dependency. You have the ability to Edit note or Delete dependency. Edit note will allow you to change the description of the dependency relationship. Delete dependency will only delete the service dependency specifically from the selected service you are currently viewing.



Service Dependencies via API

If you would like to set up Service Dependencies via API. Please visit our developer tools here under service_dependencies.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

Contact Our Support Team
Got a Question or Suggestion? We're here to help!
Follow us on Twitter
Get the latest news and updates first