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

# ntfy

> Push Observer alerts to an ntfy topic, on ntfy.sh or your own ntfy server.

[ntfy](https://ntfy.sh) delivers notifications to phones and desktops
through topics. Observer publishes each alert to a topic you choose, on
ntfy.sh or on your own ntfy server.

> [!NOTE]
>
> ntfy is an experimental channel. Like every destination other than
> email, it is available from the Starter plan.

## Set up

**1. Choose a topic**

On ntfy.sh, anyone who knows a topic's name can read it, so pick a long,
random name such as `observer-alerts-7f3k2q9x`. Topic names use letters,
digits, hyphens and underscores, up to 64 characters.

Subscribe to the topic in the ntfy app on every phone that should get the
alerts.

**2. Add the destination in Observer**

In the console, open **Alerts**, choose **Add destination**, pick **ntfy**,
and enter the **Topic**. Two fields are optional:

* **Server**: your own ntfy server, as an `https://` address. Defaults to
  `https://ntfy.sh`.
* **Access token**: for a protected topic or server. Observer sends it as a
  bearer token.

The topic and the token are stored encrypted. Under **Routing** >
**Status page**, choose **All status pages (organization-wide)** or a single
page, then select **Add destination**.

**3. Test it**

Use **Send test** from the row's actions menu. A test notification should
appear on the topic.

## Priority

Observer sets each message's ntfy priority from the alert.

| Alert | ntfy priority |
| - | - |
| A critical alert opens | 5 (max) |
| A major alert opens | 4 (high) |
| Any other alert opens | 3 (default) |
| The alert resolves | 2 (low) |
| Scheduled maintenance, SLA statement notices, daily digest | 1 (min) |

At max priority, the ntfy app can sound through Do Not Disturb when you
allow it in the app's settings.

## How alerts open and close

Observer sends one message when an alert opens and one when it resolves. A
resolve goes only to destinations that received the alert, and filters and
snooze never block it. See
[How alerts open and close](https://docs.use.observer/docs/notifications/index.md#how-alerts-open-and-close).

## Troubleshooting

* **Nothing arrives**: check that the app is subscribed to the same topic
  on the same server, and that the destination is enabled.
* **Your own server**: it must be reachable from the internet over HTTPS.
  Observer does not send to private network addresses.
* **To see what happened**: **Latest alerts**, at the top of the **Alerts**
  page, shows each delivery's result.


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