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.

We’ve added a new Inbox where notifications and nudges that were previously sent only by email are now available directly inside Monte Carlo. This includes things like:

• Being @mentioned in alert or monitor comments
• Permission upgrade requests and other action-oriented messages

Instead of managing these solely from your email client, you can now stay on top of everything in one centralized view.

You can now add notes and comments directly on monitors using the Activity section, keeping important context, discussions, and decisions in one place.

What’s new:

• You can now leave notes on monitors to add context at the point of editing / enabling a monitor
• A new Activity tab on the monitor details page that shows change log and comments
• Ability to @mention teammates in monitor comments to loop them in. Mentioned users receive an email with a link back to the monitor
• Comments are accessible also from the Monitors list view, via the selected columns

Why this matters: Monitors often evolve over time and involve multiple people. This update makes it easier to review drafts, explain changes, ask questions, and hand off ownership - all without leaving Monte Carlo.

What’s new:

• Viewers and Editors roles can now create monitors in Draft mode
• Draft status is clearly labeled in Monitors list and details page
• A new “Save as draft” option is available during monitor creation
• Draft Monitors are not running, and will not send alert notifications
• Editors, Admins, and Owners can review and enable draft monitors to start receiving notifications
• If you’re a Viewer: You can create a monitor as a Draft and share a link with a teammate to review it. This lets you propose monitors and get feedback
• If you’re an Editor, Admin, or Owner: You may receive a draft monitor link from a teammate who’s a Viewer. You can review the configuration, make changes if needed, and enable the monitor when it’s ready
• When data may be sensitive, such as Metric Monitors with segmentation, raw values are hidden for Viewers by default

Why this matters: Draft Monitors let more people contribute to monitoring. Teams can propose monitors, collaborate on the right configuration, and review changes before anything goes live - helping organizations move faster while staying in control.

Working with Validation Monitor alerts that include multiple conditions just got easier! Each invalid row now indicates which specific validation condition it matched.

The triggering condition is surfaced alongside highlighted values, with options to filter by condition and quickly navigate to the relevant column(s), making it simpler to understand what’s happening when a monitor includes several validations.

Notes just got an upgrade!

Monitor Notes appear directly in alert notifications and are often the first thing teammates read when triaging an issue.

Notes now support rich text formatting—bold, italic, underline, strikethrough, lists, links, inline code, and code blocks—you can craft clearer, more readable guidance for your team.

You can also insert the following Monitor properties as variables, adding dynamic context like last updated details and monitor tags:

• Last updated at
• Last updated by
• Priority
• Tags
• Query result(For Validation and Custom SQL monitors)

Switch your workspace to dark mode for a calmer, more comfortable experience. You can choose your theme by clicking on your user profile and selecting Light, Dark or System option under Theme.

The operations agent is more than just a chatbot - it’s brings the power of the tools in our MCP Server to users out of the box — no API keys, no setup, no configs, no external tools. Just ask.

The operations agent also partners with our support assistant, trained on our public documentation, so you can get answers to product questions directly in Monte Carlo. Learn more about the support assistant.

The operations agent is in public preview. If necessary, both the operations agent and support assistant can be disabled in the AI agents settings page. If AI features were already disabled, the operations agent will be disabled by default.