Service Dependencies Visualization

Question

We're using Compass to track service dependencies but cannot visualize infrastructure dependencies (databases, AWS services) in dependency maps. However, Compass requires all dependencies in the DEPENDS_ON relationship to be existing components with valid component IDs or slugs. This means we cannot visualize infrastructure dependencies unless we create a full component.

Questions
Can Compass visualize infrastructure dependencies without creating full components? Are there plans to support infrastructure dependencies for this one?

Expected
Ability to show service dependencies on infrastructure resources in dependency maps without full component onboarding.
Currently we can only track service-to-service dependencies, limiting visibility of complete dependency graphs.

Thank you

Enrique Serrano Valle · Answer

@Dave Mathijs 's response is accurate. Additionally, when tracking infrastructure dependencies as components, it is possible to assign a specific component type to these, so infrastructure components are easy to identify and filter out if needed.

By default, you can assign them the "Other" component type, but you can also create a custom component type such as "Infrastructure" to explicitly assign it as well.

Dave Mathijs · Answer

Hi @Nhat Tran welcome to the Atlassian Community Forums!

Atlassian Compass requires you to model dependencies through defined 'components'. Once you declare a component, you can map its upstream/downstream relationships and visualize them on the interactive dependency map.

You cannot visualize raw infrastructure resources independently, they must be represented as Compass components first.