Atlassian Opsgenie
Service-aware alerting, on-call, and incident orchestration.
Open-Source Projects
Discover top open-source software, updated regularly with real-world adoption signals.
Discover top open-source software, updated regularly with real-world adoption signals.
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.
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.
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.
It is in maintenance mode; only critical bug fixes and CVEs with a CVSS score of 7.0 or higher are addressed.
Grafana 11 or newer, with the `externalServiceAccounts` feature toggle enabled.
Set `FEATURE_PROMETHEUS_EXPORTER_ENABLED=True`, provide a secret via `PROMETHEUS_EXPORTER_SECRET`, and configure a `prometheus.yml` file as described in the README.
Yes, you can run the engine and Grafana separately, but you must provision the Grafana plugin manually via the API.
Refer to the Migration Guide linked in the repository README for steps to move to Grafana Cloud IRM.
Project at a glance
ActiveLast synced 4 days ago
