Today we are announcing Monte Carlo's foray into data observability for Teradata, starting with the ability to run SQL Rules and detect Volume anomalies. SQL Rules can be created in either the UI and/or programmatically via Monitors-as-Code (API/SDK too). These monitors can be used to generate notifications to relevant stakeholders, circuit break pipelines, and conduct RCA (e.g. sampling). Asset entries are also created in Monte Carlo and Custom Lineage APIs are available to write lineage across databases to data warehouses.

A brand new version of the incident feed has been released to all customers with the primary goal of giving users a better overview of the incidents that are surfaced in Monte Carlo. Some of the top changes and additions include:

• Table-based format: Switched from a card-based layout to a table-based layout with expandable rows to surface incidents.
• Bulk Updates: You are now able to update the status, owner, and severity of multiple incidents in one action by utilizing the check boxes to the left of each row and then dropdown buttons at the top of the page.
• Date Ranges: You can now view incidents with a start and end date by either using the presets in the dropdown menu or a custom date range of up to two months using the “custom” button.
• User Activity Section: You are now able to see and comment in the User Activity section for any incident directly from the feed.

This feature is going through a phased rollout to customers -- it is currently available in some but not all customer environments.

Notifications 2.0 is a set of improvements that make it easier to set up, manage, and maintain notifications in Monte Carlo. Key improvements:

• An audience is now an easy-to-create and easy-to-edit group of 1 or more recipients
• All kinds of notifications (custom monitors, automated monitors, digests, etc) map back to an audience
• It’s easy to create an audience on-the-fly as part of custom monitor creation

These improvements do not introduce any major new concepts. Instead, they just remove friction from the current experience. Learn more in our docs. For some customers, moving to Notifications 2.0 will require migrating notification settings.

When parameterizing values from breached rows into notifications, we now will show up to 50 values or 2,000 characters in alerts, whichever is reached first. The previous limits were 10 and 500, respectively.

Large enterprises often use ServiceNow as a point of triage for data incidents. The new Monte Carlo <> ServiceNow integration makes it easy to create ServiceNow Incidents automatically from Monte Carlo incidents. The associated ServiceNow Incidents will be linked from IncidentIQ and filterable from the Incident Feed. Read more in our docs.

Note: before you can use ServiceNow as a notification channel, you first need to integrate it in Settings > Integrations.

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.