Alert channels
Route incident notifications to your team through these integrations:Slack
Incoming webhook notifications.
PagerDuty
Events API v2 trigger-resolve.
OpsGenie
Alert API integration.
Discord
Webhook notifications.
Microsoft Teams
Incoming webhook connector.
Webhooks
Custom HTTP endpoints with HMAC signing.
Email notifications to any address.
Channel lifecycle models
Alert channels have two delivery models. Understanding the difference helps you choose the right integration:| Model | Channels | Behavior |
|---|---|---|
| Fire-and-forget | Email, Slack, Discord, Teams, Webhook | Each notification is self-contained. Incident created and resolved messages are independent. |
| Trigger-resolve | PagerDuty, OpsGenie | Opens an alert on incident creation and explicitly resolves it, maintaining state in the external system. |
CI/CD
Deploy monitoring configuration automatically from your CI/CD pipeline:GitHub Actions
Official setup-devhelm action for automated deploys.
Generic CI/CD
Use the CLI in GitLab CI, Jenkins, CircleCI, and more.
Observability
Export DevHelm data to your existing observability stack:Prometheus
Metrics export for custom dashboards.
Datadog
Unified observability dashboards.
Grafana
Visualize monitor data in Grafana.
Observability integrations (Prometheus, Datadog, Grafana) are planned. These pages will be updated when the features are available.
Next steps
Alerting overview
Understand how channels fit into notification policies.
Alerting guide
End-to-end guide for setting up alerting.