✨ New Features

dbt Impact Analysis for GitHub and GitLab

We're excited to announce the release of our first CI workflow for both GitHub and GitLab: an impact analysis workflow that uses Sifflet's lineage API to generate the potential impact of your dbt code changes and posts it as a pull request comment. With this workflow, you can detect and resolve potential issues before code changes are merged.

The potential impact consists of the list of assets downstream of the dbt model(s) you’re modifying. These assets can be other dbt models, BI dashboards, or any other asset cataloged in Sifflet.

The workflow comes packed with two filtering capabilities, using either asset types or tags to minimize noise and focus on assets that matter.

To activate this new feature, refer to the dedicated documentation for GitHub and GitLab.

Throughout the next months, we'll continue to release Sifflet-powered CI workflows that bring all of Sifflet's capabilities to your software development platform.

Manage Sifflet Credentials and Sources as Code With Sifflet Official Terraform Provider

Ensuring your data observability adapts to changes in your data environment can be challenging. With Sifflet official Terraform provider, you can now manage Sifflet credentials and sources as code, making it easy to automate their creation and maintenance. Leveraging Terraform resources also improves governance and security by simplifying versioning and auditing of any changes performed on credentials and sources.

Read more about Sifflet official Terraform provider

Secure and Private Data Observability With Private Link Support for AWS and Azure

We are excited to announce that Sifflet now supports Private Link for secure, private connectivity between Sifflet and your AWS and Azure sources. With Private Link, Sifflet can access sources located within your private network while ensuring that data traffic stays completely off the public internet. This feature allows your teams to benefit from the value of data observability regardless of your organisation's security and compliance requirements.

Read more about private links

👍 Improvements

Extended Airflow Support to Amazon MWAA and GCP Cloud Composer

Sifflet can now integrate with managed Apache Airflow environments on Amazon MWAA and GCP Cloud Composer. For setup details, you can check out the dedicated documentation:

• Amazon MWAA setup guide
• GCP Cloud Composer setup guide

More Accurate Usage Stats

Since Sifflet now inserts a JSON comment at the top of its queries, we excluded all Sifflet queries from usage stats. This ensures that usage information is more accurate and only represents your own usage.

Simplify Incident Management with Jira Status Changes Sync

You can now optionally enable status changes sync from Jira to Sifflet. This will ensure any Sifflet incident gets automatically moved to In progress or Closed • Fixed when its associated Jira issue gets transitioned to an In-progress or Done status. Enabling status changes sync allows you to benefit from Sifflet incident management troubleshooting and collaboration capabilities while ensuring a smooth incident management process thanks to automated closing of your Sifflet incidents.

Read more about Jira integration

Improve Data Trust With Sifflet Insights Browser Extension Support for Power BI Reports

Ensuring teams have access to dashboard health status while browsing their BI tools is key to ensure trust in your data. Sifflet is going one step further in improving data self-service reliability by now supporting Sifflet Insights browser extension on Power BI reports.

Read more about Sifflet Insights Browser Extension

🛠 Fixes

• Improved Model for Full Data Scan Monitors: When monitors query entire tables, the data often does not change much or have much seasonality, we've improved our models to be less noisy in these cases.
• Improvements to Monitor Pages: More coming but you'll have noticed we've started to improve the UX of the monitor page ! Enjoy!
• Improved Jira Integration: We fixed a bug that was preventing the manual creation of Jira issues in case of large number of projects and issue types on the Jira account.
• Improved Support: We've removed the ability to disable the access of Sifflet support teams to SaaS accounts to ensure optimised support experience.
• User creation: We fixed a bug that was preventing the creation of users in some specific cases.

App version: v335-347