Customers with dbt integration can now set up Github integration to gain visibility into the code impact on their data!

The Github integration allows customers to

1. See recent PR history for any tables via the catalog page
2. Check potentially relevant PRs in the context of an incident via the Incident IQ page

Follow docs here to set it up https://docs.getmontecarlo.com/docs/github

Users can now filter down the metrics in Data Reliability Dashboard only for tables with a specific tag. Multiple tags can be added and filtered on at a time with each added as an OR condition.

This is particularly helpful when trying to narrow down the tables that are included in some of the metrics in the Data Reliability Dashboard, especially when they are in a specific domain. Rather than creating a separate domain just for reporting purposes, users can now easily filter down by tags to get to the level they want.

Users can now choose which Snowflake Databases and Schemas are ingested into Monte Carlo. This adds onto our existing functionality for BigQuery, Redshift, and Databricks via CLI/API, see docs here.

Slack and Email notifications only. Docs.

Users of Monitors as Code have heavily requested a way to also manage the notifications for their monitors, without going into the UI. This makes that possible, along with all the version control goodness that comes with managing a configuration via code.

Monitor creation for SQL Rules now allows an optional “Investigation Query” to allow users build custom query for incident investigation.

Incident IQ for an SQL Rule breach shows the results of running the investigation query at the time of breach in a new tab called “Investigation rows”

. If the monitor fails while this option is enabled, a failure notification will be sent to same destinations that an Incident notification would be sent to. Read our full doc for more detail.

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.