DevEx Roundup: Instrument your catalog with the Sentry integration

[#1]

Hello Compass Community,

We’re bringing you more contextual information to your software catalog with the Sentry integration and other enhancements to Compass, your developer experience platform.

What’s included this month:

• 🎺 Instrument your catalog with the Sentry integration

• 🔎 Find what needs attention - filter components by scorecard

• 🗂️ More ways to find your components

• 🤷 Whose service is it anyway? 4 steps to reduce cognitive overhead with Compass

🎺 Instrument your catalog with the Sentry integration

The Compass Sentry integration adds application performance monitoring and error tracking to your software catalog, giving you more contextual information to reduce cognitive load. The integration adds Sentry errors and alerts to the activity feed for a comprehensive look at events affecting your components and their dependencies. The Sentry app provides an "Unresolved Sentry Issues" metric for your components.

Learn more about the integration and get started in just a few steps:

1. 💻 Navigate to your Apps UI in Compass

2. 👉 Click the install button next to Sentry app and follow the prompts

3. 🔗 Choose a Compass component and paste a link to the corresponding Sentry project

4. 🚨 Navigate to Alerts in Sentry and add the Compass "notification integration" action for relevant alerts on this component

🔎 Find what needs attention - filter components by scorecard

Scorecards help you cultivate healthy practices and identify areas that need attention. Now it’s easier to find those gaps with scorecard filtering. Compass helps you find components associated with a scorecard based on owner team, tier, component type, scorecard status, and criteria status. Log in and search by scorecard.

🗂️ More ways to find your components

Compass helps you find critical information about your components fast. We’ve enhanced how you filter components by adding Lifecycle Stage and custom fields so you have even more ways to slice and dice your data to find what you need. Log in today and try it out.

🤷 Whose service is it anyway? 4 steps to reduce cognitive overhead with Compass

Understanding who owns what is one of the biggest challenges we hear from engineering teams.

To help, we've made it easy to assign ownership of a component in our built-in software component catalog to reduce cognitive overhead, improve service health, and promote a better developer experience for your teams.

✅ Assign ownership in four quick steps:

1. 🔍 Navigate to the Components UI within Compass and select "no owner team" in the default filters

2. 👉 Select any component without an owner

3. 🚀 Click "add owner team" and select an existing team. Or, create a new team, and invite new users via the Teams UI in the top nav

4. ✅ Once you've added an owner team, you'll see an increase in service readiness and DevOps health scores associated with the component

Component ownership is a great way to promote cross-team collaboration, reduce MTTR and confusion, and improve governance, so aim to have an owner assigned to components as soon as they’re created.

---

Want to share your thoughts or ideas? Let us know with a comment below, or sign-up to chat with a Compass PM! Haven’t tried Compass yet? Sign-up today!

[Milos Ristic]

It's really great thing!I fell like I am my own boss!Great feeling managing with the things !  :)