On the main dashboard, Bigquery customers can now toggle to 2 additional metrics: Bytes Billed, Slots Used. When clicking into the details drawer of a write query, users can also see the corresponding charts for those metrics.
SQL rules users are now able to get automated suggestions for investigation queries based on how their team researched breaches of that rule in the past.
You can now push a Data Quality Warning into Tableau from Monte Carlo, on the "Reports Affected" page of an asset or an incident.
Set a message, and you can edit it afterwards. The Data Quality Warning will expire approximately 24 hours after it's set or edited.
More info in the docs here: https://docs.getmontecarlo.com/docs/tableau and about Tableau Data Quality Warnings here: https://help.tableau.com/current/online/en-us/dm\_dqw.htm
This new integration uses Alation's APIs from their Open Data Quality Initiative. Specifically, this integration populates a 'Health' section in the table-page of Alation's catalog, surfacing recent incidents and the status of those incidents. This helps keep data consumers in Alation up the date on the health and usability of their tables. See our docs to learn more.
Field Health sample rows now includes actual anomalous and normal rows to help customers investigate the anomalies. Previously in the sampling section, only historical field health metrics were shown. Now, for instance, for % unique, we are giving users not only % unique metrics overtime, but also the unique rows and non-unique rows. Similarly, for % null, we are giving users not only % null metrics overtime, but also the null rows and non-null rows.
This is currently available for field health metrics with %s. Support for percentiles and means will be added in the future.
The charts for SQL Rules with Automatic Thresholds now show an overlay of thresholds over time, with granular detail available in the tooltip. This allows for a much better understanding of what thresholds are being automatically set by Monte Carlo, building better trust between users and the system.
This commonly used metric is less prone to being skewed by outliers than mean.
This commonly used metric is less prone to being skewed by outliers than mean.
In the performance dashboard, if users click into any query details drawer for a write query, two additional charts are added alongside the run time chart and volume chart: i) partitions scanned v.s. total partition chart, ii) % scanned from cache. These are available for Snowflake accounts.
SELECT/read queries are now live in a new view called "Read Queries" in the Performance dashboard! With this feature, you'll be able to easily identify the slowest running queries across your org and use the filters to investigate particular subsets further.