Building critical data products? Sign up for our upcoming guide

— Written by Mikkel Dengsøe — 9/2/2024

PagerDuty integration, new user roles, and improved usability

New user roles

We extended our roles support with the Developer role and Business User. This makes it easier for you to collaborate with team members who need specific access to SYNQ. For example, Business Users see a simplified version of the SYNQ platform in a read-only mode to prevent them from making unintended, breaking changes.

Read more in the User Roles docs.

PagerDuty integration

It’s now possible to connect PagerDuty with SYNQ to enhance your incident management and alerting capabilities and ensure swift handling of data issues.

changelog

Key benefits include:

  • Instant Alerts: Get real-time notifications from PagerDuty when a data issue arises.
  • Quick Impact Assessment: Easily evaluate the downstream business impact of data issues (e.g., impacted data products), so your team can prioritize fixes.
  • Unified workflow: On-call responders are alerted immediately, enabling faster, more efficient resolutions that fit your existing workflows.

See our Pager Duty integration docs for more details.

Improved Code & Changes navigation

We’ve introduced several improvements to the Code & Changes tab to speed up key workflows, such as debugging issues or understanding SQL logic.

  • Our column-level lineage now tracks through which CTEs each column data goes through, allowing faster navigation.
  • We added support for displaying unused columns from SQL to highlight when they could be removed.
  • We indicate whether a column is just a passthrough from the source table, if it was renamed, or if it undergoes some function transformations.

See the improved Code & Changes workflow in action.

changelog

What else we’ve shipped

🆕 We extended our dbt catalog collection to include yaml-defined descriptions of the columns.

🆕 The Home screen now displays products in groups, similar to how they are displayed on the Products page.

🧹 Filters now behave as intended. The frontend previously returned incorrect results in some cases.