You can set alerts on all metadata that Databand tracks - everything from run durations to data quality metrics. You can configure alerts programmatically and through the Databand UI.
- In the Alerts tab in the sidebar, click the button 'Add Alert' at the top right corner of the screen.
- In the 'Add Alert Settings For Pipeline' drop-down list select a pipeline.
- Select the pre-populated values related to the selected metric.
Run alerts cover metadata from the overall pipeline/DAG execution, including overall duration and state (running/succeeded/failed).
If a run is restarted manually or automatically, its state and duration alert would be updated accordingly. For example, if a failed run with a firing failed alert is restarted, the failed alert on this run would be auto-resolved and would be re-fired if a re-run will fail.
You can define an alert on any user metric reported by task
Data health alerts cover metadata coming from tasks, operators, or functions from a pipeline. Examples include data profiling metrics like standard dev or mean from a column and custom user-defined metrics.
You can define specialized alerts that involve multiple conditions for the alert to fire. See the Advanced Alerts page for more info.
You can define your own alerts based on acceptable ranges or values, or switch on automated alerting using Databand's own anomaly detection algorithms, which will alert based on trends of metadata from previous runs.
Alert Operator List:
- Equal to
- Greater than
- Less than
- Greater than or equal to
- Less than or equal to
- Not equal to
- Value missing
- Anomaly detection (automated trend alerting)
- Range alert (You can define a range around the last value of the metric, for example a 15% interval. Fire an alert if the newly reported metric value is outside of this range.)
By default, when alert is defined or updated it would be applied on any run that happened in the last 48 hours. Unselect "Create alert on historical run" checkbox if you want an alert definition to apply on future runs only
You can view all alerts from the Alerts view:
It is possible to send alerts to Slack, Email, PagerDuty, Opsgenie, and custom webhooks. While Slack receivers can be configured via the UI, other types of receivers require manual configuration performed by the Databand Cloud Support Team.
- See Setting up Slack Notifications for the instruction on how to enable sending alerts to Slack.
- Databand uses Alert Manager under the hood. Check out the documentation for Alert Manager to understand what is possible to achieve when alerts are sent to Email, Slack, PagerDuty, and Opsgenie.
- Please contact the Databand Cloud Integration Team for help with enabling advanced receiver configuration including PagerDuty and Opsgenie (use your dedicated Slack channel for communication).
- Databand can send alerts to multiple receivers at the same time - for example, Slack and email. Databand can also filter alerts based on the project, source, and other properties. Please contact Databand Cloud Support Team for more info.
Email alerting prerequisites
You must whitelist [email protected] email address. Email alerts from Databand will be sent from this address.
If you had defined an alert on a certain task state, the alert was triggered, and then you decided to restart the Task - the previous alert will be automatically resolved, and a new one will be triggered for the Task if the new state matches the alert condition.
If you had defined an alert on run state, the alert was triggered and you decided to restart the Run - the previous alert will be automatically resolved, and a new one will be triggered for the Run if the new state matches the alert condition.
Updated 10 days ago