dbt Cloud customers can now use webhooks to get real-time notifications. Set up is simple - follow the docs here https://docs.getmontecarlo.com/docs/dbt-cloud

When creating a Jira issue from MC, we now pre-populate the ‘Summary’ and ‘Description’ of the issue with details from the Incident. Users would frequently need to copy & paste this information into their Jira issues, so automating this step saves them a few minutes.

Users with the Domains Manager role take on some of the work that previously only Account Owners could do, such as inviting and removing users, setting up authorization groups, and creating/editing domains. This is ideal for managers or team leads who will assist in administration of domains and users.

Users can now give a display name to a Recipient in Notification Settings. This is helpful for notification channels that normally display as long alpha-numeric strings or URLs, like MS Teams, webhooks, private Slack channels, Pagerduty, and Opsgenie etc. These display names propagate to anywhere else where notification recipients get shown, like Incident IQ and custom monitor wizards.

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.