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
Default Configuration
Schedule Settings
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 detectionedr monitor --slack-token $SLACK_TOKEN --slack-channel <slack_channel_to_post_at>: Sends Elementary alerts to your Slack channel
Environment Variable ConfigurationBefore using this template, you must configure the
$SLACK_TOKEN environment variable and specify your Slack channel:- Navigate to Settings > Environment Variables in Paradime
- Add a new variable named
SLACK_TOKEN - Set the value to your Slack bot token
- Save the configuration
- Replace
<slack_channel_to_post_at>in the command with your actual Slack channel name (e.g.,#data-alerts)
- Type: Scheduled Run (Cron)
- Cron Schedule:
0 */2 * * *(Every 2 hours for regular monitoring)
For custom Trigger configurations, see Trigger Types documentation.
- 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.