Now available: Interactive map view for your dependencies!

[#1]

👋  Hey everyone, Horace here from the engineering team.

A while ago, we started exploring different ways to display information about component dependencies and shared a concept of a visual dependency map. The concept got a lot of love, and so this week, we've released our first version of the dependency map! 🎉

In addition to the pre-existing list view, you can now visualise your dependencies in an interactive, component-centric view, with a focus on each component's direct dependencies. In the first version, you can view basic information about each component, such as its description and when it was last deployed, and traverse the map to understand the interdependencies amongst all of your components.

We’ve already heard some compelling suggestions from you — displaying more and more varied information like labels and announcements, or even active incidents. Also high on the list is a zoomable “canvas” view. Keep the ideas coming!

We had a blast bringing this concept to life, and are super excited to see where this goes next. Let us know what you think! What else would you like to see on the dependency map? 👀

[David Berclaz]

Hi @Horace Kuan 

I wanted to try it on my Compass instance (dberclaz) but couldn't figure out how to switch from List to Map, as I don't see the toggle displayed on your screenshot. Is it already deployed on all Compass instances?

Cheers,

David

[Horace Kuan]

Hi @David Berclaz, sorry to hear that the view switcher wasn't displaying.

We've just deployed a change to make sure the dependency map is available on all instances. Can you give it another try and let us know how it goes? You might need to clear the browser cache if a simple page refresh doesn't work.

[David Berclaz]

@Horace Kuan > It's working now, thanks!

[Mircea Braescu]

This is great. The next step would be some sort of higher level overview

[Peter Camfield]

The ability to show all dependencies (or dependencies to n depth) would be really compelling. We are modelling our (grouped) message queues as Data pipeline components so we can trace through the components involved in a flow.
Would be good to have the labels change to Subscribes from / Publishes to instead of Depends on / Depended on by when viewing a component of type Data pipeline. Also may be worth adding a  new component type for this common scenario - something like Messaging component 

[Fong]

Hello Compass Community,
I believe that having a high-level dependency mapping would be incredibly beneficial.
Is this feature still included in the product roadmap?