10.11.21 Changelog

We're making progress on

What's new

• SQL Rule Incident card redesign: To make it easier to understand what is driving SQL Rule breach, we added a historical rows returned graph and link to the SQL Rule detail view
• Query Graph: Released a new view that graphs SQL queries by character length to visually show when queries change and consequently help in an investigation

Improvements and fixes

• Resolved query parser errors: A small number of query parser errors were fixed to improve reliability of how we generate lineage
• Support multiple monitors on single table graphs: Now that we moved the Field Health and Dimension Tracking graphs to the monitor detail view, we can support multiple monitors on a single table that have different configurations resulting in different graphs

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
• Field level lineage: We're working on a way to expose field level lineage in the UI to help with both field-specific investigations and field deprecation