Alert channels

A channel is a delivery destination for alerts. Each integration has its own doc with setup detail; this page is the channel reference.

supported channels

• Slack — slack:#oncall. See slack-integration.
• PagerDuty — pagerduty:routing-key-name. Routes via integration key. See pagerduty-integration.
• Opsgenie — opsgenie:team-name. See opsgenie-integration.
• Microsoft Teams — msteams:channel-name. See ms-teams-integration.
• Email — email:oncall@example.com. Plain SMTP delivery.
• SMS — sms:+15551234567. Twilio under the hood.
• Webhook — generic HTTP POST. See webhook-integration for payload schema and HMAC verification.

creating a channel

devflow channels add payments-oncall   --type pagerduty   --routing-key R012345

Or via Terraform — devflow_channel in terraform-provider.

attaching to a monitor

alert_channels:
  - slack:#payments-oncall
  - pagerduty:payments-oncall

You can attach as many channels as you like. They fire in parallel.

attaching to an SLO

SLO alert rules attach to channels the same way — see slo-multi-window-alerting.

severity routing

Channels can be filtered by severity:

alert_channels:
  - { type: slack, target: "#payments-oncall", severity_min: warning }
  - { type: pagerduty, target: payments-oncall, severity_min: critical }

This routes everything-and-up to Slack and only criticals to PagerDuty. See alert-routing for the full routing primitives.

quiet hours

Channels (especially email/SMS) can have quiet hours. See notification-throttling.