For breached SQL rules, users are now not limited to 500 rows cap when trying to download breached rows. Instead, users can go to the breached rows tab and click on "Run Query and Download CSV" to run the SQL rule live and download up to 10k rows breached.

We previously required customers to have dbt integration before setting up Github integration, to allow mapping from pull requests to models to tables. Now, dbt integration is no longer a prerequisite. All customers that use Github can set up the integration. Customers without dbt integration will still see the most recent PRs in IIQ before the incidents, with the limitation that they will not be able to filter for PRs based on tables or see PRs mapped to the asset page.

When query change is detected for an incident, users can now click on the "compare queries" link at the end of the insight banner on the query logs page to directly compare the pre and post change queries.

Users can now create Custom Auth Groups for the Account Owner and Domains Managers roles. Custom Auth Groups can then be mapped to SSO Groups. Previously, the Account Owner & Domains Managers roles could only be applied through default Auth Groups, which could not be mapped to SSO.

If a user creates or links a Jira issue from an Incident, a log of that activity is passed back to any Slack notifications that were sent out, increasingly visibility.

The status of a custom monitor is now broken down into three categories:

• Run history
• Model training status
• Misconfigurations

This gives clearer insight into what might be wrong if your monitor has not been operating as desired.

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.