Data Product Lineage

While we bring lineage to a new level—by blending column-lineage and code—we are now making it easier to understand how your Data Products depend on each other. Our new product-level lineage acts as an abstraction of underlying details to highlight product-level dependencies and creates a new high-level overview of the data stack.

In the above example, we can see our in-app analytics data product, depending on several tables and models from three upstream data products that are closely aligned with the producers of the data. It’s a simple high-level end-to-end overview.

Opsgenie integration

Unify your alerting and on-call management in one place – you can now tie issues from SYNQ to Opsgenie to prioritize data issues alongside other production-grade issues.

Learn more about our Opsgenie integration in our docs.

Column descriptions propagated across data assets

We improved the discovery of the descriptions from related data assets. For example, if we find a description for a column in a dbt model, we automatically display it on the linked data warehouse table.

Product filters now includes folders

The product filter now includes folders, mirroring the functionality of the browser filter. You can select individual items or entire folders, and folder selection automatically includes all products within that folder.

What else we’ve shipped

🆕 On the issue and incidents page you can now toggle to only display open issues

🆕 Lineage in products now has filters enabled

🆕 Data Products now display folder info if present

🧹 Limit for filter groups has been raised from 5 to 15

🧹 Product items in impact lists now display priority

🧹 Fixed lineage side panel not redirecting to the correct page when closing with the X button

🧹 Fixed asset count displaying 0 when all assets should be counted