Historically, Metric Monitors supported bucketing data by hour and by day. We now also support bucketing by week and month, making it much easier to monitor sparse or infrequently updated data. For example, if a financial institution wants to do anomaly detection on data they get from an external partner once/month, that is now much easier to do than before.

In addition, when bucketing by week or month, the monitor now backfills much more historical data than before in order to understand seasonal trends. Up to 3 years of history is backfilled when bucketing by week, and up to 10 years when bucketing by month.

For customers with many warehouse integrations, in SQL monitors creation view, MC now automatically filter the warehouse list by domain, so users will only see the warehouses mapped to the assets in the domain selected on top.

Warehouse options for a domain with MySQL & Salesforce assets only

For customers on consumption pricing plans, Monte Carlo now sends an email summary of consumption once per month to all Account Owners. It includes detail from the previous month about credits consumed, credit rate ($), commit consumed ($), and amount due ($). This email is typically sent around the 5th of the month, but may be received off-cycle as well if you undergo a change in pricing plan.


It is possible to customize the recipient list of this email by clicking the Email statements button in the Current running statement section.

For many of our customers who use SQL rules for data quality, getting a full list of all rows violating the rule is critical, as internal teams need to follow up on each and every one of them. When SQL rules were launched, we limited the number of rows to 500 per alert in order to constrain scale/complexity. This has just gotten a lot better! Users now have access to up to 5,000 rows when a SQL rule alerts.

Please note: requires reaching out to our support team to raise account level limits. The default remains 500 rows per alert.

For customers that use Redshift data sharing for sharing data between producer and consumer clusters, MC can now support lineage between such clusters and allow custom monitoring on each.

See docs here for more details