# Prometheus Alertmanager to Pagerless

> Paste one URL into Prometheus Alertmanager. Pagerless decides who to wake, explains it in plain words and closes the problem when Prometheus Alertmanager says it's fixed.

URL: https://pagerless.dev/integrations/prometheus-alertmanager
Updated: 2026-10-22

## Set up

Your URL is in the Pagerless app under Other tools, with the key filled in:

```text
https://events.pagerless.dev/v1/hooks/alertmanager/<your ingest key>
```

1. **Open alertmanager.yml, a webhook receiver** In Prometheus Alertmanager.
2. **Add a receiver pointing at your Pagerless URL.** 
3. **Route your alerts to it, with send_resolved: true.** 

```yaml
receivers:
  - name: pagerless
    webhook_configs:
      - url: https://events.pagerless.dev/v1/hooks/alertmanager/<your ingest key>
        send_resolved: true
```

## What happens

| When | Pagerless |
| --- | --- |
| Fires | Each alert with status firing (one problem per alert in a group) |
| Clears | Status resolved |
| How loud | The `severity`, `priority` or `level` label |
| Proof it's you | The key in the URL is the proof. `npx pagerless connect` can write a receiver that reads the key from a credentials file instead. |

## Choosing who gets woken

| Rule | Example |
| --- | --- |
| Name rules on the URL | `?wake=prod-*&log=*-staging` (globs, case-insensitive) |
| The tool's own severity | critical, p1, sev1, fatal wake; error, warning tell; info, low log |
| A default on the URL | `?level=wake` (or tell, log). Without one: tell. |

`?service=` and `?env=` set the service and environment shown on the problem.