Query logs now has a brand new look with major changes below

• query graph and query table now displayed in one view, with color legend for each query
• query graph y-axis showing query count per day instead of query length
• checkboxes available next to queries in the query table so users can easily select 2 for comparison
• in cases of query-based insights, those queries are highlighted in both graph and table for easy spotting
• added user and type filter for queries

more self-evident across Monte Carlo. These are most effectively used as a means to route notifications to the correct recipients.

We have now added the ability to view the history of returned row count for each dbt test failure in the form of a chart.

Users can now download the breached rows from a SQL rule breach as CSV via the Incident IQ page under Breached Rows tab.

Customers can now ensure that monitor schedules adapt to time changes caused by daylight savings. This feature can enabled as part of the monitor creation flow by flipping the toggle and selecting a regional timezone.

For freshness rule breaches, a freshness update chart is now available in the incident card, so users can quickly obtain context on the incident table's freshness update history visually.

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.