> ## 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.

# Works with your pager

> Observer does not run on-call schedules. It sends each alert to the tool that pages you, and closes it when the problem recovers.

Observer reads your metrics, decides when something is wrong, runs your
status pages and keeps the record of each incident. It does not run on-call
schedules, escalation policies or phone calls. Keep the tool that pages your
team: Observer sends it every alert and closes the alert when the problem
recovers.

## Pick a destination

| You page with | Observer destination | When a critical alert opens |
| - | - | - |
| PagerDuty | [PagerDuty](https://docs.use.observer/docs/notifications/pagerduty.md) | A PagerDuty incident opens at `critical` severity and your escalation policy pages. |
| Splunk On-Call | [Splunk On-Call](https://docs.use.observer/docs/notifications/splunk-on-call.md) | A Splunk On-Call incident opens. |
| Grafana IRM | [Grafana IRM](https://docs.use.observer/docs/notifications/grafana-irm.md) | A Grafana IRM alert fires. |
| Phones, without an on-call service | [Pushover](https://docs.use.observer/docs/notifications/pushover.md) | An emergency notification repeats every minute until someone acknowledges it. |
| Phones, through ntfy | [ntfy](https://docs.use.observer/docs/notifications/ntfy.md) | A max-priority notification arrives. |
| Another tool | [Signed webhook](https://docs.use.observer/docs/notifications/chat-and-webhooks.md) | Observer posts a signed JSON event for your own receiver to forward. |

Pushover and ntfy are experimental channels. Every destination other than
email is available from the Starter plan.

## What stays with Observer

* **Deciding**: a metric turns unhealthy only after its threshold holds for
  the confirmation time you set, so a single bad sample does not page anyone.
  See [Thresholds and confirmation time](https://docs.use.observer/docs/concepts/thresholds-and-dwell.md).
* **Closing**: when the metric recovers, the alert closes in your pager. A
  close is never blocked by filters or snooze. See
  [How alerts open and close](https://docs.use.observer/docs/notifications/index.md#how-alerts-open-and-close).
* **Telling customers**: the status page and its subscribers get the
  incident, which you can scope to the customers it affected.
* **The record**: what was measured during the incident stays with it, for
  SLA reports and reviews.

## Choose what pages

Each destination chooses its own alerts. Under **Alerts**, the **Paging**
preset sends what should wake someone, and **Custom** lets you choose the
alerts yourself. Under **Routing**, narrow a destination by services, metrics
and minimum severity. A team can send critical alerts to its pager and
everything else to a chat channel.

## Moving off an on-call tool

If the tool you page with is being retired, move paging first, then connect
Observer to the new tool. For Grafana OnCall OSS, see
[Move off Grafana OnCall OSS](https://docs.use.observer/docs/guides/migrate-from-grafana-oncall.md).


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