You can now schedule monitors to run immediately after your ETL jobs complete, reducing time-to-detection (TTD) from hours to minutes. Whether you use Airflow, dbt, or other supported orchestration tools, Monte Carlo can trigger monitors as soon as a job finishes successfully.

Snowflake users may now raise monitor query timeouts up to 1 hour directly from the UI.

• Enables compute-intensive monitors (e.g. full-table duplicate checks) to reliably complete
• Provides flexibility to balance runtime vs. warehouse size
• Reduces wasted compute from monitor failures due to timeouts

Support for BigQuery, Redshift, and Databricks is in progress.

Note: raising the timeout increases usage of your Snowflake warehouse. Use longer timeouts only when needed to avoid unnecessary spend.

Comparison monitor is now available for Salesforce CRM. This allows users to ensure integrity of data flowing from CRM to warehouse. Docs.

You can now connect Monte Carlo to Datadog Incident Management. Create or link incidents directly from alerts, sync status and ownership automatically, and add Datadog as a notification channel.

https://docs.getmontecarlo.com/docs/datadog

We've released much better support for "Chargebacks", a common need in enterprises who wish to attribute consumption & cost back to the appropriate lines of business. Detailed documentation is available here.

Specifically, we have shipped a new Consumption data export which details consumption by monitor for the last 30 days. This can be easily joined to the Monitors data export using monitor_id, which allows enterprises to trace credit consumption back to particular creators, domains, audiences, etc. Different enterprises have different processes for how they manage and trace chargebacks, so this flexibility is important.

This is only available for customers that meet BOTH of the following conditions:

• Are on a consumption pricing plan
• Are on the new version of Table Monitors. You are on the new version if your account was created after July 2, 2025 or if Table is a monitor type available to you in the Monitor Menu.

When receiving an alert from Monte Carlo, the troubleshooting agent can automatically work through 100s of hypothesis and highlight the ones that are most likely to have caused the issue. It will consider changes in the data, system issues (e.g. Airflow or dbt failures) apd code changes when analyzing an alert, and will automatically traverse lineage to identify the root cause.

Learn more in the Troubleshooting agent documentation.

When a user tries to open an alert they don’t have permission to view, Monte Carlo now provides a clear path forward with an Access Request option. Here’s how it works:

• Users can request access directly from the landing screen
• Account admins are notified by email of the request
• Admins can decide whether to update the user’s role or group to grant access
• Once permissions are updated, the user is notified by email and can return to the alert

We hope to streamline the process of getting unblocked, both by giving users a clear way to request access and by reducing the back-and-forth in organizations where it isn’t obvious who to contact. At the same time, access decisions remain fully in the hands of admins, ensuring the right level of control.

Advanced Monitors now fully support SAP HANA, enabling users to leverage Data Profiler and Monitoring Agent recommendations, as well as deploy metric, validation, and comparison monitors on their SAP HANA assets.

Learn more about SAP HANA support

MC shipped a series of improvements to the domains creation experience -

1. Users can now exclude assets in addition to include.
2. Users can use tags along with assets selection
3. New UI: the domain creation workflow got a brand new look, which includes a tree navigation and side-by-side assets v.s. selection summary.

We're launching a brand new concept for our alert pages, across all alert types. This is a complete makeover of the page that improves clarity, usability and overall user experience. Some of the highlights of the new page include:

• Less clutter, more focus on the information our users are most interested in when triaging/troubleshooting – specifically the chart/details of the alert
• Critical triage actions are placed in the navigation bar – still very accessible, but taking less real estate and attention away from core information about the alert
• Grouped events now have a more intuitive and concise visual representation
• [coming soon] This page will be AI-native... Troubleshooting agent will become a more organic component of the page, using the space under the alert as a canvas for conversations