We've added a slider for the Freshness and Unchanged Size model on the Freshness and Volume pages of the catalog. This allows you to extend the acceptable delay to up to 72 hours for tables which you don't want to be alerted on as frequently.
A new version of the CLI (v0.31.0) is released where each of the toggle-*-events commands is replaced with a pair of configure-*-events and disable-*-events commands. Having enabling vs disabling as their own CLI commands will make such commands more clear to users.
.
Users can now snooze dbt model errors or test failures from Slack. Once snoozed, such events will not trigger additional notifications for the selected time period (12 hours, 1 day, 2 days, 3 days, or 1 week).
Users can now hover over any lineage node and see a summary tooltip showing the node's name, type, row count, and last update time. This will make it even easier for users to use lineage for troubleshooting.
To streamline the creation of monitors, we now auto-generate names based on selected tables and fields.
To help you better configure monitors, we added in-line validation to show when defined thresholds are configured to immediately start breaching. This validation is currently supported in SQL Rules and Freshness SLOs.
An "Include Normalized" filter is now available on the incident feed. Users can apply the filter to narrow the incident feed to only incidents that have not automatically normalized and still require resolution. An incident is only categorized as normalized if all events in the incident have been normalized.
Note: "Anomaly Normalized" was previously released as an incident status that could be both automatically updated and manually updated. That incident status feature was removed and "normalized" is now an independent filter. Any incidents that were previously automatically updated with "normalized" status now have no status. Any incidents that were previously manually updated with "normalized" status now are automatically updated to "fixed".
Monte Carlo now displays the maximum and minimum volume thresholds with in the a tables catalog page within a specific volume tab. This volume threshold can be turned on or off from a table of contents below the graph and when hovered, the minimum and maximum values are visible.
Volume thresholds are not shown on the incident view, only on the catalog view.
We completely redesigned the monitor creation flows taking them from a multi-step wizard to a single page where all the configuration options are displayed in collapsable modules.
- Made field descriptions editable
- Added recent usage widget to Catalog table detail summary view
- Add query count by user summary to Query Logs module