Send Elementary alerts to Slack

This template creates a schedule to execute your dbt™ models and tests, then sends Elementary data observability alerts to Slack. It helps data teams monitor data quality issues and pipeline failures with automated notifications directly in their Slack channels.

Key Benefits

• Automated data quality monitoring with Elementary's comprehensive observability

• Real-time alerts delivered directly to Slack channels

• Catch data issues early with integrated testing and alerting workflow

• Centralized team collaboration around data incidents

Prerequisites

• Scheduler Environment is connected to your data warehouse provider

• Elementary dbt package installed in your project

• Slack bot token configured

• Environment variable $SLACK_TOKEN configured in Paradime

• Slack channel name specified

Default Configuration

Schedule Settings

Setting	Value	Explanation
Schedule Type	Standard	Ensures consistent execution for production workloads with integrated alerting
Schedule Name	elementary slack alerts	Descriptive name indicating Elementary alerting to Slack
Git Branch	main	Uses your default production branch for stable monitoring

Command Settings

The template uses a sequence of commands that test, and monitor your data pipeline:

• dbt test: Runs configured data tests including Elementary's anomaly detection

• edr monitor --slack-token $SLACK_TOKEN --slack-channel <slack_channel_to_post_at>: Sends Elementary alerts to your Slack channel

Environment Variable Configuration

Before using this template, you must configure the $SLACK_TOKEN environment variable and specify your Slack channel:

1. Navigate to Settings > Environment Variables in Paradime

2. Add a new variable named SLACK_TOKEN

3. Set the value to your Slack bot token

4. Save the configuration

5. Replace <slack_channel_to_post_at> in the command with your actual Slack channel name (e.g., #data-alerts)

For detailed Slack app setup and token generation instructions, see our Slack alerts guide.

Trigger Type

• Type: Scheduled Run (Cron)

• Cron Schedule: 0 */2 * * * (Every 2 hours for regular monitoring)

For custom Trigger configurations, see Trigger Types documentation.

Notification Settings

• Email Alerts:

  • Success: Confirms pipeline completion (Elementary alerts sent separately to Slack)

  • Failure: Alerts when the schedule fails to complete

  • SLA Breach: Warns when execution exceeds expected duration

Elementary alerts are sent directly to Slack and are separate from Bolt's email notifications.

---

For advanced Elementary configurations and test types, refer to the Elementary documentation.