Users can now filter for specific Airflow DAGs to include in an audience so only alerts on selected DAGs will be sent to the notification channels for the audience to minimize potential alert noise. Previously, an audience got either all or no airflow dags’ alerts.
Users can also select specific Airflow DAGs to include in a domain, and then leverage the defined domain to define an audience. This ensures users are only seeing the DAGs relevant to them across the UI.
Docs here https://docs.getmontecarlo.com/docs/airflow#monte-carlo-notifications-of-airflow-failure-alerts

For Azure resources or deployments that are not publicly accessible, or if you prefer to connect privately, you can now utilize private endpoints! This ensures that traffic between the Monte Carlo Platform and the service traverses the Microsoft backbone network.

Supported integrations and deployments include:

• Databricks on Azure
• Snowflake on Azure
• Azure SQL Database
• Azure Agents
• Azure Data Stores

For setup instructions, check out the documentation here.

To learn more about Azure Private Link, visit this page.

We updated to a first-class PagerDuty by adding bi-directional status sync and customizing Urgency per Audience. If you are using PagerDuty already today, this will be a major enhancement to the data operations experience. If you are not using the integration, these enhancements may be unblocking!

Learn more in the video below and in our PagerDuty docs.

Marking and tracking incidents is best practice for data teams looking to improve data quality and trust across the business. Incidents should be communicated out to stakeholders when appropriate and reviewed on a monthly cadence to determine where gaps in data quality may lie. Furthermore, severity levels of incidents are useful for understanding impact quickly and setting priorities for data teams.

This change is gradually rolling out to Monte Carlo workspaces over the next week. Learn more about marking incidents and severity here in the docs!

Didn't everything used to be called an incident in Monte Carlo? Yes! See more about that recent change under Introducing: Alerts.

The "Investigating" Alert Status has been renamed to "Acknowledged." This is a minor change ahead of the Incident management changes coming soon. Read more about incident management changes on Introducing: Alerts.

Note: As of now, this is a UI change as well as Slack / MS Teams. The Monte Carlo API and Insight Reports will still show the value as Investigating. In the future, this will be changed to Acknowledged when new APIs are released.

Automated freshness, volume, schema change monitoring are now available in beta for SQL Server. Please reach out to the MC team if you are interested in getting access.

For existing SQL Server connections, an extra permission GRANT VIEW SERVER STATE is needed for the MC service account users per docs here

Tags from dbt models (incl. meta configs) are now shown in dbt alerts!

Our lineage now shades all unmonitored tables gray. This can help highlight where you might have coverage gaps in your monitoring strategy.

Assets which are "lineage only" -- those that cannot be actively monitored, such as BI Reports -- will also show up with a white background.

To add monitoring coverage, a few options:

• Click on the unmonitored table node, and our recommendation engine might suggest the best way to monitor, such as with a Data Product
• Create a Data Product that includes the unmonitored table, and monitor that table
• Or go straight to our usage page, and add custom rules for monitoring configuration

We have added an option to create volume rules from the asset page!

• Our asset page now includes three widgets: Time since last update, Time since last row count change and Change in row count with their respective graphs.
• We've simplified the process of creating volume rules by enabling users to set manual thresholds through the two new widgets: Time since last row count change and Change in row count.
• We've improved the graphs related to these metrics.

More detail on these changes can be found at Volume monitor

We've said goodbye to the "Uptime" charts on the Data Reliability and Data Product Dashboards. We're working on something new instead, so let us know if you have needs around this type of reporting!