View the historical trend for each metric displayed in the Field Profile tab. Click on any metric to expose the graph.
Snowflake comments will no longer be ingested and surfaced in UI as tags. Comments will still be ingested as table Descriptions.
We launched 2 new query-based RCA insights to help users speed up root cause analysis:
- Empty query insight: A query can run successfully but produce empty results. Empty query sight uncovers such hidden queries to help users more quickly understand why the table didnât update.
- Failed query insight: queries can fail due to timeout, poorly written code, missing fields referenced, permission issues etc. Failed query insights surface that the query updating the incident table has failed and the reason why it failed.
These insights are currently available for Snowflake accounts only. Other warehouses will be supported soon.
We now support triggering SQL Rules with variables via Circuit Breakers. Previously only the first variable would fire when triggered via Circuit Breakers resulting in partial testing. Learn more here.
A daily digest which notifies a customer of tables which are no longer being actively tracked by our Freshness, Volume, and Unchanged Size detectors. The Notification provides a link to a pre-filled freshness or volume rules so that the customer may cover the table with a custom rule.
In Settings > Notifications > Daily Digests > Digest Options, we now provide the option of Inactive Monitors. When enabled, the customer will receive a notification when a tables OOTB detector goes inactive for too long.
User's now have a new option to Snooze until breach condition resolves or changes which will drastically reduce the number of repeat custom monitor alerts a user receives.
This can be used through either the UI or through the Slack Integration
Users are now able to split events from incidents. This feature allows customers to separate events deemed unrelated so they can manage their workflow separately, i.e. assign different priorities, statuses, owners.
In the Incident IQ page of a freshness rule breach, users can now see a tab "Run History" which displays the run history of the freshness rule monitor.
The default dbt event grouping behavior puts model and test failures from the same dbt run into one MC incident. Now with this new option, customers can choose to also group "repetitive" dbt failures (same model/test + same table + same error message) into the same MC incident.
A repetitive failure will be grouped into existing incidents until it runs successfully again, or fails with a different error message.
Looking to better manage and track SLAs with Monte Carlo? Pass Rate helps you visualize how often the conditions of a Freshness, Volume, or SQL Rule have been met. For example, you could say with confidence that “we delivered this data successfully 98% of the time this quarter.”
The Pass Rate section is viewable for SQL Rules, Freshness Rules, and Volume Rules. It plots results of the rule (either pass or breach ), grouped by day, week, month, or for the overall time range you've selected.