Monte Carlo now supports more granular configuration of data sampling at the integration level.

In addition to disabling sampling for an entire integration, you can now disable sampling for specific databases, schemas, tables, or tagged assets — while keeping sampling enabled elsewhere. These controls are fully available in the UI.

For more advanced use cases, the API also supports inclusion-based configurations, allowing you to explicitly define which assets are eligible for sampling

Learn more here: https://docs.getmontecarlo.com/docs/configure-data-sampling

Turn Operations Agent YAML response into a Draft monitor in one click!

Previously, when the Operations Agent suggested a monitor, it returned a YAML definition. Now, you can create a Draft Monitor directly from the chat - no copy-paste.

What’s new:

• When the Operations Agent returns a monitor configuration as YAML, use the "Create Draft" button to convert it instantly into a Draft monitor
• The draft opens in-product, where you can review, edit, and share with teammates

We’ve introduced a new Weekly Digest to help you stay on top of what happened in your data. Each week, you’ll get a curated summary that highlights what mattered most in your environment, with direct links to dig deeper.

What you’ll see:

• A snapshot of alerts and incidents from the past week
• Visibility into unresolved issues and monitors that may need attention
• Insights scoped to your domains and responsibilities, where possible
• A quick look at how your team handled issues during the week

**Take action in one click:**Every stat in the email is clickable and takes you straight to a filtered view in Monte Carlo, so you can review details, investigate issues, or make updates right away.

Make sure you’re subscribed to receive it. If you opted out in the past, you can update your preferences anytime in your Profile settings.

When you create a new monitor, you’ll now receive an email once it completes its first run, so you know whether it’s working as expected.

What to expect:

• ✅ If the first run succeeds, you’ll get a confirmation that it completed successfully, along with a clear path to review results
• ⚠️ If the first run fails, you’ll receive a notification with a link to review and fix the issue

Each email includes a direct link to the monitor details page, where you can: Review the results / Adjust thresholds or settings / Re-run the monitor if needed.

The notification is sent once per monitor (excluding drafts or disabled monitors), and you can unsubscribe at any time.

What’s changed:

• Settings have moved to the main navigation footer (behind the cog icon).
• Billing is now in your account navigation, in the footer behind the avatar icon, so you can access it directly without going through Settings.

You can now favorite assets in Monte Carlo to keep the Assets you care about most close at hand.

What’s new:

• Mark an asset as a Favorite
• Quickly access your Favorite assets on Assets page

Monte Carlo alerts can now be sent to FireHydrant, bringing data quality issues into your team's existing incident management workflow.

To set this up, create a generic webhook event source in FireHydrant, copy the webhook URL, then add FireHydrant as a recipient in Monte Carlo (Settings > Notifications and audiences). Paste in your webhook URL, send a test notification to verify, and you're all set!

See the docs for details: https://docs.getmontecarlo.com/docs/firehydrant

Define your monitoring logic once - like tracking nulls in *_id fields or monitoring duplicate counts in email fields - and apply it to the relevant tables across your data.

Choose tables individually, by warehouse, database, or schema, and use filters like table name patterns, asset tags, and activity level. Use pattern-based field matching (e.g, "ending with _id" or "containing timestamp") to apply metrics across many tables.

As new tables are created that match your criteria, they're automatically included - so your coverage scales with your data!

See our docs for more details: https://docs.getmontecarlo.com/docs/metric-monitors#creating-multi-table-metric-monitors

Monte Carlo now natively supports Starburst Galaxy and Starburst Enterprise, including freshness and volume (opt-in), schema and metric monitors, comparison/custom/validation monitors, and partial lineage.

See the docs for details: https://docs.getmontecarlo.com/docs/starburst

It’s now easier to spot where important assets aren’t fully monitored - and take action before issues are missed.

Monte Carlo now surfaces Coverage Gaps across the product to highlight assets that have had recent issues but aren’t covered by monitors.

What you’ll see:

• Coverage gap indicators on Assets ⚠️
• A section on Coverage Dashboard that shows the top affected assets, scoped to the domain you’re viewing

How it works:

• Coverage gaps are based on recent activity (e.g., missed anomalies within the past 7 days), and asset importance
• Clicking into a gap lets you preview potential issues in context
• From there, you get a clear, fast path to enable monitoring for the asset

Why this matters: Coverage gaps help you proactively identify blind spots on your most important data. Instead of discovering missing monitors after something breaks, you can see where coverage is incomplete and address it directly.