A new tab is now available Monitor Details called Change Log, that shows the history of changes to that monitor since it was created.

This was built to help answer a few common problems from customers:

• “This monitor looks different… did something change? Who changed it?”

• “We need to track changes for compliance reasons.”

  • Historically, we’d suggest Monitors-as-Code for this use case. Now it's possible for monitors made through the UI as well.

• “Based on how this monitor is configured today, it didn’t do what I expected when an issue occurred 6 weeks ago. Was something changed since then?”

Changes are logged automatically. No configuration needed. Logging starts June 22, 2023, so changes from before then are not logged.

Previously, Pause was only available for Field Health and Dimension Tracking. Now renamed Disable, this option is available for all Custom Monitor types.

A disabled monitor won’t run, won’t gather metrics, won’t trigger incidents, and won’t send notifications. It remains in this state indefinitely until a user re-enables it or deletes it.

This is in contrast to ‘Snooze’, where a Rule will continue to run & gather metrics (incurring compute costs), but won’t create incidents or send notifications.

There are many reason to Disable a monitor, such as:

Still developing/iterating on the rule

Treating it as a template

Want it ‘off’ while your refactoring pipelines for weeks/months and don’t want it racking up queries

. The previous limitation was just 1 field.

2\. When using segments, users can now monitor up to 300 fields for anomalies. The previous limitation was just 1 field.

These improvements help you more easily identify anomalies and more quickly find the root cause.

The chart experience for SQL Rules and Field Quality Rules has been refreshed. The new look and feel allows for more better navigation and easier interpretation of the metrics being displayed by these monitor types.

For Field Quality Rules, specific attention was paid to show the right number of significant figures into the chart tooltips, so the exact details of the rule breach could be easily understood.

The chart experience for Dimension Tracking monitors and incidents has been refreshed. The new look and feel allows for more better navigation and easier interpretation of the metrics being displayed by Dimension Tracking.

All email notifications have gone through a formatting refresh to make them more:

• Interpretable: fewer words, clearer word choice, and more intuitive placement of links
• To-the-point: anomaly or breach information is conveyed sooner, often directly in the subject line
• Impactful: parameterized values from SQL rules are now formatted more clearly, allowing you to clearly convey breached row information into the email

When a user opens a PR, they will now receive a message from MC bot that displays an impact analysis of the PR, where we show a summary of directly impacted models, downstream impacted models, and impacted BI reports. Impacted key assets will show stars next to them. Users can expand to see full list as well as click into MC UI from any of the listed assets.

When logging in at https://getmontecarlo.com/signin, users now see a single field to input their email or account identifier. The app then serves the user the appropriate SSO or password login experience.

This avoids a common issue where users would attempt to log in with a password when SSO had been activated for their account.

Three UI/UX changes have improved user's ability to navigate and interact with Incidents that have associated Jira issues. Users can now:

• Filter the Incident feed for just Incidents with an associated Jira issue
• See the Jira issue from the Incident card on Incident feed
• See the owner and status of the Jira issue from Incident IQ

Inactive Monitors to their channels in Microsoft Teams. Previously, just Slack and Email were supported.