Send Elementary alerts to MS Teams

SendElementary data observability alerts to Microsoft Teams after your dbt™ runs

This template creates a Bolt schedule to send Elementary data observability alerts to Microsoft Teams. It helps data teams monitor data quality issues and pipeline failures with automated notifications directly in their Microsoft Teams channels.

Key Benefits

• Automated data quality monitoring with Elementary's comprehensive observability

• Real-time alerts delivered directly to Microsoft Teams 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

• Microsoft Teams webhook URL configured

• Environment variable $CHANNEL_WEBHOOK configured in Paradime

For this Elementary schedule to work, you will additionally need to configure the $CHANNEL_WEBHOOK environment variable. Check our full guide here.

---

Degault configuration

Schedule Settings

Setting	Value	Explanation
Schedule Type	Standard	Ensures consistent execution for production workloads with integrated alerting
Schedule Name	elementary ms teams alerts	Descriptive name indicating Elementary alerting to MS Teams
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 --teams-webhook $CHANNEL_WEBHOOK: Sends Elementary alerts to your Microsoft Teams channel

Environment Variable Configuration

Before using this template, you must configure the $CHANNEL_WEBHOOK environment variable:

1. Navigate to Settings > Environment Variables in Paradime

2. Add a new variable named CHANNEL_WEBHOOK

3. Set the value to your Microsoft Teams webhook URL

4. Save the configuration

For detailed webhook setup instructions, see our Microsoft Teams 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 Teams)

  • Failure: Alerts when the schedule fails to complete

  • SLA Breach: Warns when execution exceeds expected duration

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

---

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

---