Deadline: After we launched the new dbt data ingestion pipeline for our dbt integration in Nov 2022, majority of our customers have migrated onto the new pipeline. We are planning to deprecate the legacy pipeline 7/1/2023, so the remaining dbt core customers who have not migrated will need to update their dbt core integration setup by 6/30/2023 in order to continue to use their dbt integration.

Other reasons to migrate now:

• All new features released Jan 2023 onwards on dbt integration are only available on the new pipeline, i.e. repetitive failure grouping, job level configuration for incident generation
• dbt run logs for dbt core only available on the new pipeline
• Fix the bug where we show duplicate events for the same failure
• Fix the bug where we associate dbt errors to the wrong table when the same dbt model exist in different schemas
• Fix the bug where we skip generating certain dbt incidents when we couldn’t correctly map models to the right tables

Instructions to update your dbt core integration: https://docs.getmontecarlo.com/docs/dbt-core#modify-your-production-dbt-cicd-workflow-%EF%B8%8F-updated

Customers now define the required namespace field in the .yml files instead of defining it as part of the CLI apply command. Namespaces can be defined in the montecarlo.yml file, or within individual monitor definitions.

We now group events not only based on schema and timestamps but also based on lineage relationships. Related events can now be grouped together if they are connected via direct lineage relationships, even if they are from different schemas.

While reviewing incidents in the incident feed, users can now filter for incidents with key assets with the "Key Asset Only" filter.

Audiences are a commonly used way to organize custom monitors and route their notifications. To support this, we’ve released an Audience Manager which can be used to create, rename or delete audiences, and see which monitors are associated with an audience.

Labels have become a frequently used way to route Notifications from custom monitors to the appropriate destinations. This release moves labels into their own section in monitor creation, and gives visibility to where notifications will go when a given label is added.

Labels are created in the Labels Manager and linked to notification destinations in Notifications. Once set up, this allows users to self-serve the destinations for notifications, but adding their team's label to a monitor.

In addition to the high correlation insights we currently have available for volume addition anomalies, we now provide such insights for volume deletion cases. In incidents that caught abnormal numbers of rows deleted, users will now start seeing high correlation insights (whenever detected) to help identify potential root causes.

SQL Rules, Freshness Rules, or Volume Rules can sometimes stay in a 'breached' state for an extended period of time. Users now have options to control how often they want to be alerted in these scenarios, so they can reduce or eliminate repetitive notifications and stay on top of recent issues. See docs.

In the dbt tab in Incident IQ, users can now filter and search for dbt model runs and tests results by model names.

Expanded the ability to view and copy the YAML definition to all monitor types. These definitions help teams use Monitors as Code by exposing exactly how the in-app configuration options map to MaC definitions.