11.8.21 Changelog
almost 4 years ago
Another week of exciting developments to improve observability into Monte Carlo and further reduce false positive incidents!
What's new
- Freshness next update thresholds: Added visual thresholds to Freshness graphs which show when our anomaly detection models expect the next table update to occur
- Notification filter exclude support: Add support for excluding schemas, tables, tags, etc to help refine which notifications get sent to each channel - for example, send notifications for all tables in a schema that do not have a
in_dev:truetag
Improvements and fixes
- Field Health and Dimension Tracking Monitor Suggestions: Released 2 new insights reports that provide recommendations on which tables and fields to apply both FH and DT custom monitors on based on importance and similarity to previously configured monitors
- Anomaly detection model improvements: Released a set of changes to improve recall and precision of notifications to further reduce false positives
- Improved SQL editor UX: When editing SQL for SQL rules, users can now expand the editable space to support bigger queries and format them easier
What's next
- Spark lineage: For our Spark customers, we're working on launching lineage which will allow you to map how queries interact to form lineage
- Circuit Breakers: Trigger Monte Carlo data quality checks and validate incidents with code to stop problematic jobs before they pass data downstream