Set Up Events for Automated Failure Notifications

Problem Overview

Without automated notifications, detecting a data quality failure requires someone to actively check HEDDA.IO after every pipeline execution. In organizations with multiple pipelines running throughout the day, this is impractical. Failures go unnoticed until downstream systems or business users surface the problem - often hours or days later, and after bad data has already been processed further.

Solution

HEDDA.IO's Events system connects pipeline outcomes to external notification channels. An Event Sink defines the destination - Teams, Slack, email, Azure DevOps, or others. An Event defines the trigger and references the sink. When the trigger condition is met, HEDDA.IO dispatches the notification automatically. No polling, no manual checking.

HEDDA.IO supports the following notification channels:

Configuration

Create an Event Sink

1. Open the Project and navigate to the Events tab.
2. Click Add Event Sink in the left panel.
3. Select the Sink Type and fill in the connection details. For Teams, provide the Webhook URL. For Azure DevOps, provide the organisation name, project name, Personal Access Token, and the work item type to create.
4. Save the Event Sink.

For Azure DevOps, set the Work Item Type to 'Bug' (or a custom Work Item type) for Dataset Rule failures. This places data quality incidents directly into your team's backlog alongside software defects, with the same priority and triage workflow.

Create an Event

1. With the Event Sink saved, click Add Event.
2. Select the Event Sink.
3. Choose the trigger. Common options: 'Execution Completed' for a post-run summary, 'Dataset Rule Failed' for immediate threshold breach alerts, or 'Knowledge Base Published' to notify downstream teams that a new configuration is live.
4. Select the Knowledge Base
5. Configure the message template or payload and save.

Outcome

After configuration, the Event Log tab in the Project Navigation Bar provides a complete history of every dispatched notification. Each entry shows the event type, the Knowledge Base and Run involved, the timestamp, and the delivery status. Use the Edit Log Filters button to narrow the log by event type, status, or date range when investigating a missed notification.

If you have any further questions, please feel free to Contact Us.