The Data Reliability Dashboard now contains a new tile allowing users to see the total number of tables that are being monitored across all integrations in one easy to access number. A historical trend of this total is available as well.
This tile is only available when viewing "All Domains".
(Note: the historical trend will only be available from the the last week of March going forward. Prior total table count will not be available in the historical trend chart.)
Today, we expanded coverage across the board to close the gaps on Volume monitoring. You can now simply opt-in to Volume monitoring for any External Table and View, as well as any Table on Data Lakes. This collection of Row Count drives both the Unchanged Size and Volume Change Detectors, which will both start training immediately once enabled. More controls for these monitors are coming soon!
Today we are enabling the ability to store the Monte Carlo sampling data in your cloud for both GCP and AWS. This is a new deployment option to store the Object Storage bucket directly in your cloud environment. This is available both for AWS (S3) and Google Cloud (GCS).
More information on Deployment Options is now available in the documentation.
The clickpath to get to the monitor through Incident IQ is a bit cumbersome and hard to find. For users that want to jump right to the associated monitor from Slack, this cuts to the point much quicker.
Users can now add Exclusion Windows directly in the UI in Settings > Muted Data and Filters > Exclusion Windows. Monte Carlo's anomaly detection models will ignore the timeframes set by exclusion windows. Use this to protect the anomaly detection models from one-off integration issues or vendor service outages. Learn more in our docs.
Starting September 21, all new custom monitors created through the Monte Carlo UI will have Failure notifications defaulted on. Previously, this was defaulted "off" for newly created monitors.
This means that if the monitor times out, fails to execute, etc, Monte Carlo will send a notification about that failure. The notifications go to all the places that that monitor would normally send, and they are sent in close to real time (1-2 mins). Learn more in our docs.
A "last modified by" field has been added for custom monitors in the monitors details page. A "last modified at" time field is also available for SQL rules monitors. In addition, the "created by" field, which used to update when monitors are modified, is now fixed and will not update anymore.
BI tools tend to have a lot of content named similarly - with this release we added some information about the hierarchy of each asset in asset search results and the top of the Asset page. We also added an icon for the specific type of asset as well as a column in the search result to make it easier to find what you are looking for.
Looker
Power BI
Tableau
We're steadily refreshing all the notification formats in MS Teams to align with what's worked well in our Slack integration. Most recently, we've updated the formats for all rule notifications (SQL Rules, Freshness Rules, Volume Rules, and Field Quality Rules). These deliver information in a more digestible and intuitive format.
With the release of the Asset page side-nav a couple months ago, users can now access Asset pages for projects and datasets. These pages were pretty sparse.
Weâve reformatted them to look cleaner, and added a tabular view to browse the tables within. This shows the tables' Importance Score, reads/write per day, and count of distinct users, helping users understand which tables are heavily used, and which aren't.
