> ## Documentation Index
> Fetch the complete documentation index at: https://docs.use.observer/llms.txt
> Use this file to discover all available pages before exploring further.

# Move off Grafana OnCall OSS

> Grafana OnCall OSS was archived on 24 March 2026. Move paging to a supported tool and run status pages and customer updates on Observer.

Grafana OnCall OSS entered maintenance mode on 11 March 2025 and was
archived on 24 March 2026. Its repository is read-only, and the
Cloud-connected SMS, phone and mobile push notifications stopped working for
self-hosted installs. Grafana's recommended path is Grafana Cloud IRM; see
Grafana's [OnCall OSS migration guide](https://grafana.com/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/oncall-oss/).

Observer is not an on-call tool: it has no schedules and no escalation
chains. This guide covers how to connect Observer to the tool you move
paging to, and the parts Observer adds: status pages, customer updates and
a measured record of each incident.

## What moves where

| In OnCall OSS | After the move |
| - | - |
| Schedules, escalation chains and routes | Your new on-call tool: Grafana Cloud IRM, PagerDuty or Splunk On-Call |
| Integrations that receive alerts | Your new on-call tool. To drive status pages from the same alerts, also send them to Observer (step 3). |
| SMS, phone calls and mobile push | Your new on-call tool's app, or Pushover or ntfy from Observer for a small team |
| Telling customers | Observer status pages and their subscribers |

## Steps

**1. Choose where paging lives**

Move schedules and escalation chains to the new on-call tool. For Grafana
Cloud IRM, follow Grafana's guide linked above. A small team without
schedules can page phones directly with [Pushover](https://docs.use.observer/docs/notifications/pushover.md)
or [ntfy](https://docs.use.observer/docs/notifications/ntfy.md).

**2. Connect Observer to it**

In the console, open **Alerts** and add a destination for the tool you chose:
[Grafana IRM](https://docs.use.observer/docs/notifications/grafana-irm.md),
[PagerDuty](https://docs.use.observer/docs/notifications/pagerduty.md),
[Splunk On-Call](https://docs.use.observer/docs/notifications/splunk-on-call.md),
[Pushover](https://docs.use.observer/docs/notifications/pushover.md) or [ntfy](https://docs.use.observer/docs/notifications/ntfy.md).
Pick the **Paging** preset, then use **Send test** to confirm a test alert
reaches it.

**3. Give Observer the same signals**

Status in Observer comes from metrics. Either point Grafana Alerting at an
Observer inbound source, so the alerts you already have drive status pages
([Receive alerts from your monitoring](https://docs.use.observer/docs/guides/inbound-alerts.md)), or
let the agent read your metrics directly
([Define your first metric](https://docs.use.observer/docs/quickstart/first-metric.md)).

**4. Publish a status page**

Create a page, add the services your customers see, and let them subscribe.
See [Publish your first status page](https://docs.use.observer/docs/quickstart/first-status-page.md).

**5. Test end to end**

Make one metric unhealthy, for example by firing an alert that one of your
mapping rules routes to an alert-backed metric. Check that the new on-call
tool pages, that the status page shows the problem, and that the alert
closes in the on-call tool when the metric recovers.

**6. Retire OnCall OSS**

Stop OnCall OSS only after the new on-call tool has paged someone for a test
or a real alert.

## Related

* [Works with your pager](https://docs.use.observer/docs/notifications/works-with-your-pager.md)
* [How alerts open and close](https://docs.use.observer/docs/notifications/index.md#how-alerts-open-and-close)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.