You now have the ability to hide queries from the performance table and chart so that you can only view the queries you care about. This can be done through the "eye" icon on the table or by utilizing a new filter called "Query" where you can deselect any queries that are not relevant.

Selectors for Metric Segment and Date are now all conveniently aligned across the top, making interacting with the metrics collected by the Field Health Monitor much easier.

For enterprises with multiple Monte Carlo environments, the same email can now be a user in more than one account. This makes it easier for admins who need to be present in multiple accounts, who'll no longer need a distinct email address for each.

For the vast majority of customers, Domains meets their needs for creating separate workspaces or teams. But in some cases, leveraging multiple Monte Carlo environments is a compelling alternative.

You can now interact with the IIQ page and its tabs whilst having the User Activity section in-view. This makes it a lot easier to jot down notes, as well as refer to previous comments posted on the incident and comments from similar past incidents too.

User can now select specific metrics to monitor within Field Health. By selecting just specific metrics, users can perform more targeted monitoring that are executed more efficiently.

Note, for new field health monitors, there are now just 4 metrics selected by default: % null % unique % zero mean. Additional metrics will need to be opted in.

Previously in the assets page we were only showing pull requests related to a table that were merged within the last 7 days. Now customers can see all past PRs up to the time when the Github integration was set up.

For Field Health monitors with segmentation fields selected, the initial execution of the monitor will now collect metrics from the trailing 7 days. This jumpstarts the training of the machine learning detectors, shortening the amount of time they need to 'warm up' and allowing users to receive meaningful anomalies, faster.

You'll see this on the Assets page, Incidents, Freshness and Volume Rule builder, and anywhere else where Freshness or Volume charts are displayed. The new look and feel allows for more better navigation and easier interpretation of the metrics being displayed by these monitor types, including:

• Adjustable time-window slider on the X-axis
• Cleaner, more reactive, and more informative tooltip
• Synchronized actions between Freshness and Volume charts on the Assets page

Referential Integrity is a common test to ensure that the values in a field always have corresponding records in another table. For example, make sure that the customer field in orders table all have a matching customer in the customer_fact table.

You can now set these up through Monte Carlo without needing to write any SQL.

MC is releasing a brand new dashboard with the aim of helping you understand performance issues in your data stack. The dashboard allows you to explore the performance of "write" queries run in the past 4 weeks with a number of different filters as well as dig into each query’s deeper context through a detail drawer with volume correlation, runtime breakdown, and other metadata. This is currently only enabled for Snowflake customers, however, we plan to release the dashboard for BigQuery and Redshift soon.

To use the Performance Dashboard, please click on the Performance tab in the MC UI.

For more information about the Performance dashboard, please visit https://docs.getmontecarlo.com/docs/performance-beta