Atlassian Opsgenie
Service-aware alerting, on-call, and incident orchestration.
Grafana OnCall
Self-hosted incident response with Slack, SMS, and phone alerts
Developer-friendly on-call management that aggregates alerts, schedules rotations, and sends notifications via Slack, Telegram, SMS, and phone. Deployable via Docker or Helm.
Overview
Highlights
Multi-channel notifications (Slack, Telegram, SMS, phone)
Dynamic on-call schedules with automatic escalations
Seamless Grafana UI integration via plugin
Docker‑compose and Helm chart ready deployments
Pros
- Easy self-hosted setup with Docker/Helm
- Rich Slack and chat integrations
- Supports Prometheus metrics exporter
- Works directly within Grafana UI
Considerations
- OSS version in maintenance mode, no new features
- Requires Grafana 11+ and feature toggle
- Limited official support
- Migration to Cloud IRM needed for long-term roadmap
Managed products teams compare with
When teams consider Grafana OnCall, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Teams already using Grafana who need on-call scheduling
- Small to medium DevOps groups looking for self-hosted solution
- Hobby projects or proof-of-concept deployments
- Organizations comfortable managing Docker/Helm environments
Not ideal when
- Enterprises requiring active maintenance and SLA guarantees
- Users needing the latest incident-response features
- Environments that cannot run Grafana 11 or newer
- Teams that prefer a fully managed cloud service
How teams use it
Self-hosted on-call rotation for a startup
Alerts from Prometheus trigger Slack messages and automatic escalations, keeping engineers on-call without external services.
Phone and SMS notifications for critical incidents
On-call engineers receive immediate voice calls or SMS, reducing mean time to acknowledgement.
Integrating custom monitoring via Prometheus exporter
Metrics are scraped by Prometheus and displayed in Grafana, while the OnCall engine routes alerts based on those metrics.
Migrating from legacy on-call tool
Using the provided migrator, teams import schedules and contacts, transitioning to Grafana OnCall with minimal disruption.
Tech snapshot
Python77%
TypeScript22%
Go1%
Smarty1%
Makefile1%
Starlark1%
Frequently asked questions
Is Grafana OnCall OSS still receiving updates?
It is in maintenance mode; only critical bug fixes and CVEs with a CVSS score of 7.0 or higher are addressed.
What version of Grafana is required?
Grafana 11 or newer, with the `externalServiceAccounts` feature toggle enabled.
How do I enable the Prometheus metrics exporter?
Set `FEATURE_PROMETHEUS_EXPORTER_ENABLED=True`, provide a secret via `PROMETHEUS_EXPORTER_SECRET`, and configure a `prometheus.yml` file as described in the README.
Can I run OnCall without Docker?
Yes, you can run the engine and Grafana separately, but you must provision the Grafana plugin manually via the API.
Where can I find the migration path to Grafana Cloud IRM?
Refer to the Migration Guide linked in the repository README for steps to move to Grafana Cloud IRM.
Project at a glance
Active- Stars
- 3,864
- Watchers
- 3,864
- Forks
- 375
LicenseAGPL-3.0
Repo age3 years old
Last commityesterday
Self-hostingSupported
Primary languagePython
Last synced 12 hours ago