We've implementing some changes around how an Asset looks when it is not currently enabled for monitoring by Monte Carlo. Users now will be able to access more card on the Summary page, access the Monitors tab as well as run the Data Profiler for that table.

In addition, we've added other helpful way to get unmonitored tables enabled for monitoring. If you have access to the Usage UI, clicking "Enable" on an unmonitored table will provide a list of suggested ways you could get a table enabled for monitoring. Selecting one of these options will automatically add a rule in the Usage UI and enable the table for monitoring.

We've dramatically improved the anomaly detection for "Time since last row count change" in Metric Monitors. This enables customers to do more sensitive freshness monitoring for highly segmented use cases.

The model now produces more sensitive thresholds, and generates thresholds faster as well.

For example, this would be very helpful if you have multiple versions of an app, each sending events back to the same table, and you wanted to be alerted if any version went abnormally long without sending any events.

We've improved our rule in the Usage UI to let users include/exclude tables by last activity. Now, users can specify "read", "write" or "read or write" activity and select from 7 to 31 days for lookback.

As an example, this rule could be used to include all tables from a certain schema with recently changed data (recent write activity).

For more details on the Usage UI, refer our docs

The settings view now has a new look! The previous tabular layout is replaced with tiles, making the UI more intuitive and easier to navigate. No functionality changes.

Following up on our recent improvements to Volume alerts, we've released a similar set of improvements for managing Freshness alerts (time since last update & time since last row count change). Same as the Volume release, we’re rolling this out gradually over the next few weeks. It is currently available to just a subset of customers.

Specific improvements:

• Freshness thresholds don't automatically widen after an anomaly. Instead, anomalies are excluded by default from the set of training data. If they don’t want to be alerted to similar anomalies in the future, users can ‘Mark as normal’. This will re-introduce the anomalous data point to the training set and widen the threshold.
• Users can 'select training data' directly in the freshness chart. This gives the user full control over which data is used to train the model, without needing to navigate to Settings to create Exclusion Windows.

With this change, all anomaly detection in Table monitors (Freshness & Volume) now behaves the same way. Anomalies are excluded anomalies by default from the data set that trains thresholds. And users can then choose to add them back in if they’d like to widen the threshold.

Read more about interacting with our anomaly detection.

In addition to the existing workflow of sending alerts to ServiceNow via audiences, users can now minimize alert noise within their ServiceNow environments by manually reviewing alerts before forwarding them or linking alerts to existing ServiceNow incidents.

We've redesigned the monitor list and added new bulk actions, filtering, and sorting capabilities to simplify a variety of monitor management workflows such as:

• Sorting monitors by alert frequency and bulk disabling or snoozing noisy monitors to reduce alert fatigue
• Sorting monitors by run and bulk editing their schedule configuration to spread out monitor runs
• Sorting monitors by last run to review and bulk delete stale monitors
• Bulk running monitors to test newly created ones quickly
• Adjusting the columns and displaying the information that matters most to each user

You can now configure monitor alert notifications and monitor failure notifications with different audiences in order to route issues to the appropriate stakeholders while minimizing noise and alert fatigue.

Last year, we released a big set of improvements to the Metric monitor that improved anomaly detection and the user experience on the Alert page. As part of this, we released a new metric property in Monitors as Code and the API.

Users have still been able to create monitors under the old “field_health” property, though its use to create new monitors has dwindled.

As of March 1, 2025:

• Users will no longer be able to create new monitors using the field_health property. Existing monitors using that property will continue to function without interruption and will still be editable. When creating new Metric monitors, users should use the metric property instead. The differences between the field_health and metric properties are modest, and a guide for how to navigate the two is here.
• Users will no longer be able to use the createOrUpdateMonitor mutation to create a Metric monitor via the API/CLI. Customers should use createOrUpdateMetricMonitor mutation instead. Existing monitors will continue to function without interruption.

We're simplifying how users provide feedback to our anomaly detection models.

Up until recently, users had the option to "Share feedback" on any Alert in Monte Carlo. If the user marked the anomaly as "Helpful" in that workflow, then Monte Carlo would remove that anomaly from the set of data that was used to train thresholds. This would then restore thresholds to pre-anomaly levels.

This workflow has been deprecated and removed. Rationale:

• This workflow had a duplicative effect to marking the alert status as "Fixed". Having multiple workflows with the same effect was confusing.
• We're transitioning to a model where anomalies are excluded from training by default, and users can add them back in through a "Mark as normal" workflow. Read more.

Read more about how to interact with our anomaly detection here.