If you're encountering issues with unrelated events being consolidated into your notifications (e.g., in Slack or MS Teams), it's crucial to understand the current functionality and explore potential solutions:
Currently, notification settings serve as criteria to match with a full incident. Consequently, the Notification message generated and sent includes all events within a matching incident that meets the notification setting criteria. We don't presently filter out specific events within the incident notification message that don't meet the criteria.
However, the capability to filter out individual events that don't directly match the Notification setting criteria is an open feature under consideration: PRO-1225.
As a temporary workaround, customers may consider disabling incident grouping, ensuring each incident comprises a single anomaly or affected table. Before implementing these methods, it's advisable to assess the potential impact on the notification volume, as this action will very likely lead to an increase in notifications. We provide two API methods for disabling incident grouping:
- toggleIncidentGrouping: Disables all incident grouping in a warehouse.
- toggleSchemaChangeIncidentGrouping: Disables schema change incident grouping.
Comments
0 comments
Please sign in to leave a comment.