Аutomatic alerts allow you to define specific alerts types for each pipeline that originated from a specific source. Instead of manually definition alerts on every pipeline this method allows easy and time-effective way to create and manage multiple alerts.
Automatic alerts are defined on a source level. Go to Settings->Airflow Syncers. You can define automatic alerts during syncer creation or edit existing syncer definitions and enable auto alerts.
You can see the respective alert definitions on the alert definition screen. They would appear in a global alert definition and pipeline specific alert definition screens
The following types of Аuto Аlerts are supported:
- State alert - An alert will be triggered when any run for any pipeline running on the specified syncer fails.
- Duration - An alert would be triggered when any run for any pipeline running on the specified syncer has an anomaly in run duration.
- Schema Change - An alert would be triggered when for any dataset with schema reported from a pipeline running on a specified syncer.
For each alert type and every source, one alert definition would be created. For example, it would be one alert definition responsible for triggering alerts on run failures from a specific source.
In order to disable these alerts a user can:
- Delete alert definition from alert definition screen
- Edit a Syncer from Settings->Airflow Syncers table and disable auto alert there.
When an alert definition is deleted, existing firing alerts would be deleted as well.
- alert would be fired on any pipeline from a source
- all existing pipelines would be affected
- new pipelines coming from a source would be affected as well
When Syncer is archived, automatic alerts associated with a syncer are deleted.
Updated 29 days ago