We've published a new CLI version (v0.26.3) that includes support for customers who have single-tenant dbt Cloud. Users can now provide a --dbt-cloud-base-url option when setting up the dbt Cloud integration.
Users can now add multiple data lake connections. This specifically is useful for customers with multiple Databricks Workspaces, Multiple Glue Catalogs in different AWS accounts or Regions, and other complex Data Lake scenarios. Reach out to your CSM to get access!
Snoozing allows you to stop a monitor from creating Incidents for a predefined amount of time. With this update, we expanded Snoozing support to Volume and Freshness SLOs, and allow you Snooze monitors from Incident IQ.
Users can now easily see if any dbt model errors or test failures exist for upstream or downstream tables directly on both lineage and pipelines views. Users will also be able to see the list of dbt errors in the catalog page for a table.
Users can now trigger SQL Rules to run using the SQL Rule name, instead of the MCON which can change. This feature is available in the latest version of PyCarlo and our airflow-mcd provider.
Added support for enabling a Databricks integration from the MC app. Previously, users were only able to set up Databricks via the CLI.
Custom monitors Volume SLIs and Freshness SLIs are renamed to Volume SLOs and Freshness SLOs, respectively, with the goal to more accurately reflect the fact that those custom monitors define data quality objectives for customers to meet.
We've redesigned catalog pages to make them easier to navigate and find what you're looking for.
-
Individual Pages
- Left hand navigation
- Removed unnecessary buttons on lineage
- Removed unnecessary date picker on Query Logs
- Tags have been moved to General Information Tab
Adjust your field health metrics to adjust the sensitivity resulting in a decrease or increase in generated Incidents.
Medium Sensitivity is the default value. High sensitivity will result in more Incidents, while low sensitivity will result in fewer Incidents.
As a follow-on to the recent Databricks announcement, we released Volume SLO (total bytes) support to drive further parity across all data platforms.