Audiences are a commonly used way to organize custom monitors and route their notifications. To support this, weâve released an Audience Manager which can be used to create, rename or delete audiences, and see which monitors are associated with an audience.
Labels have become a frequently used way to route Notifications from custom monitors to the appropriate destinations. This release moves labels into their own section in monitor creation, and gives visibility to where notifications will go when a given label is added.
Labels are created in the Labels Manager and linked to notification destinations in Notifications. Once set up, this allows users to self-serve the destinations for notifications, but adding their team's label to a monitor.
In addition to the high correlation insights we currently have available for volume addition anomalies, we now provide such insights for volume deletion cases. In incidents that caught abnormal numbers of rows deleted, users will now start seeing high correlation insights (whenever detected) to help identify potential root causes.
SQL Rules, Freshness Rules, or Volume Rules can sometimes stay in a 'breached' state for an extended period of time. Users now have options to control how often they want to be alerted in these scenarios, so they can reduce or eliminate repetitive notifications and stay on top of recent issues. See docs.
In the dbt tab in Incident IQ, users can now filter and search for dbt model runs and tests results by model names.
Expanded the ability to view and copy the YAML definition to all monitor types. These definitions help teams use Monitors as Code by exposing exactly how the in-app configuration options map to MaC definitions.
View the historical trend for each metric displayed in the Field Profile tab. Click on any metric to expose the graph.
Snowflake comments will no longer be ingested and surfaced in UI as tags. Comments will still be ingested as table Descriptions.
We launched 2 new query-based RCA insights to help users speed up root cause analysis:
These insights are currently available for Snowflake accounts only. Other warehouses will be supported soon.
We now support triggering SQL Rules with variables via Circuit Breakers. Previously only the first variable would fire when triggered via Circuit Breakers resulting in partial testing. Learn more here.
