DevHelm integrates with your existing tools for alerting, incident management, CI/CD, and observability. Set up an integration once and reference it from your notification policies or CI/CD pipelines.Documentation Index
Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt
Use this file to discover all available pages before exploring further.
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
DevHelm does not currently export metrics to external observability platforms (Prometheus, Datadog, Grafana, etc.) — these integrations are not on the roadmap at this time. If you need DevHelm data inside another tool today, you have two options:- Webhooks — push incident events to any HTTP endpoint with HMAC-signed payloads.
- REST API — pull monitor results, uptime stats, and incident history into your own pipeline.
Next steps
Alerting overview
Understand how channels fit into notification policies.
Alerting guide
End-to-end guide for setting up alerting.