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
We added the ability for users to easily explore each lineage node via clicking on the node and bringing out a slide-out, where users will find the table's freshness and volume charts, query logs, usage info, and tags & descriptions.
Users can now use CRON expressions when defining the schedule of a SQL Rule. This option is available when using Absolute and Relative thresholds but not when using Automatic thresholds.
To dramatically increase performance and reduce compute of MC-generated queries, we released a feature that automatically detects partition logic in tables for query optimization. This feature enables us to expand the RCA correlation analysis to data lakes and increases the performance of our Field Health and Dimension Tracking monitors running on partitioned tables.