Users with the Account Owner role are now notified via email when an integrations fails a critical validation for collecting Metadata and Query Logs across Warehouse & Databricks integrations.

This new rule type allows users to create checks for:

• Allowed values let me know if any values other than \[list\\] are present
• Never-missing values let me know if any of \[list\\] values are not present
• Count distinct set expectations for the number of distinct values in a column

The functionality is currently in beta. Users will see a 'Cardinality Rule' option on the custom monitor menu, but note that once a user finishes the creation flow, it will produce a SQL Rule.

In Incident IQ page of a SQL rule breach, under Investigation Rows tab, if there are rows returned from the investigation query, a button on the top right allows the data to be downloaded as CSV.

In Incident IQ, the Past Incidents tab now displays incident status and # of tables for each past incident.

Previously only available via our API, Fivetran can now be set up through MC UI. Under Settings -> Integrations users can now set up Fivetran connections.

The charting experience in Field Health has been modernized, making it smooth and more intuitive to navigate and understand field health anomalies and analytics.

Query change insights are now available on tables upstream of incident tables, expanding the root cause insights MC can detect from incident table only to further upstream.

Whenever MC detects any query change upstream of an incident, a banner will show up on incident feed and incident IQ pages alerting the insight detection. From the query logs tab in Incident IQ, users will be able to select not only incident tables, but also upstream tables from table selector, to view query change details.

To help eliminate any confusion between the functionality of Monte Carlo versus a more traditional enterprise data catalog, the Catalog tab has been renamed to Assets. There's no change to the functionality or roadmap of that part of the product -- this is merely a design change.

Today we are announcing Monte Carlo's foray into data observability for transactional databases, starting with the ability to run SQL Rules on MySQL, Postgres, and Microsoft SQL Server. SQL Rules can be created in either the UI and/or programmatically via Monitors-as-Code (API/SDK too). These monitors can be used to generate notifications to relevant stakeholders, circuit break pipelines, and conduct RCA (e.g. sampling). Catalog entries are also created in Monte Carlo and Custom Lineage APIs are available to write lineage across databases to data warehouses. Please reach out if you have additional use-cases for these transactional databases!

For customers who have integrated Jira to Monte Carlo, you can now start the flow to convert an Incident to a Jira issue directly from Slack. This increases visibility of this time-saving feature.