Skip to main content
Every alert can be sent to one or more destinations. You can send an alert straight to specific channels, route it through an owner so it follows team ownership, or do both on the same alert. The available destinations are Slack, email, Microsoft Teams, and webhooks (including PagerDuty and Opsgenie).

​
Send directly to channels

When you create an alert in Settings → Alerts, you pick where it goes on the Targets step — no owner needed. Add any mix of:
  • a Slack channel
  • a Microsoft Teams channel
  • one or more email addresses
  • a webhook, including PagerDuty and Opsgenie

Choose where an alert is sent — Slack, Microsoft Teams, email, and webhooks, in any combination.

This is the simplest way to route an alert: the alert knows where it goes, so you can see and change its destinations in one place. Use it for alerts that don’t belong to a single team — for example a company-wide freshness alert to #data-alerts, or a webhook that opens a PagerDuty incident.
Not every destination is offered for every alert. Slack and Microsoft Teams are available for issue and schema-change alerts, email for every alert, and webhooks for issue alerts.

​
Route through an owner

Instead of naming channels on the alert, you can send it to an owner. The alert then goes to all the channels that owner has set up — its Slack channel, Microsoft Teams channel, email addresses, and Coalesce Quality users. You set those up on the owner (see Setting up alerts and Tagging owners). Alert routed to #operations-data-team title Routing through an owner is handy when you want alerts to follow team ownership: change the owner’s channel once and every alert sent to that owner follows. You can also give the same assets more than one owner to alert several teams at once.