# Alertmanager vs PagerDuty: Qual para Alerting?

> Alertmanager vs PagerDuty: um roteador de alertas open-source para Prometheus vs uma plataforma gerenciada de resposta a incidentes. Roteamento, on-call e ajuste a CI comparados.

Source: https://latchkey.dev/pt/learn/tool-comparisons/alertmanager-vs-pagerduty  
Updated: 2026-06-26

Alertmanager roteia, agrupa e silencia alertas do Prometheus; PagerDuty é uma plataforma gerenciada de resposta a incidentes com escala de on-call e escalonamento.

Alertmanager cuida da deduplicação, agrupamento, silenciamento e roteamento de alertas do Prometheus para receivers, mas não é uma plataforma completa de on-call. PagerDuty adiciona escalas de on-call, políticas de escalonamento, workflows de incidentes, analytics e integrações com centenas de ferramentas como um SaaS pago. Eles são complementares: Alertmanager vence no roteamento de alertas open-source; PagerDuty vence na resposta a incidentes end-to-end e na gestão de on-call.

## Comparison

|  | Alertmanager | PagerDuty |
| --- | --- | --- |
| Tipo | Roteador open-source | SaaS gerenciado |
| On-call | Não (só roteia) | Escalas + escalonamento |
| Gestão de incidentes | Mínima | Workflows completos |
| Custo | Gratuito (self-host) | Pago por assento |
| Melhor para | Roteamento do Prometheus | On-call + incidentes |

## Caso de uso e escopo

Alertmanager serve a equipes que querem roteamento de alertas gratuito e self-hosted fortemente atrelado ao Prometheus. PagerDuty serve a organizações que precisam de rodízios de on-call, escalonamento, workflows de incidentes e analytics. Um padrão comum roteia alertas do Alertmanager para o PagerDuty na camada de resposta humana.

## Ajuste a ops e CI

Alertmanager é um pequeno binário self-hosted que você opera; PagerDuty é totalmente gerenciado. A config e as regras de roteamento do Alertmanager costumam ser validadas no CI, onde runners gerenciados mais rápidos aceleram testes de config e linting de regras.

## Decide with your own numbers, not a feature table

Feature comparisons age badly and rarely decide anything, because both tools in a mature category can do the job. What differs is how each behaves on your repository, and that takes one afternoon to measure.

```Terminal
# time a cold install with each candidate, cache cleared
hyperfine --prepare "rm -rf node_modules" --warmup 1 \
  "<tool-a> install" "<tool-b> install"

# and the thing CI actually pays for: a cold run with no local cache
docker run --rm -v "$(pwd):/w" -w /w node:22 sh -c "<tool> install"
```

> Measure the cold path. Warm local benchmarks favour whichever tool you already have cached, which is exactly the condition a CI runner never has.

## What actually changes when you switch

- Lockfile format. A switch is a one-way door for anyone still on the old tool until everyone migrates, so plan it as a single coordinated change.
- Resolution strictness. Tools differ on whether an undeclared transitive import works, and the stricter one will surface latent bugs as new failures.
- CI cache configuration. The cache path and key differ per tool; carrying over the old ones silently disables caching.
- Everyone on the team and every runner must move together. Pin the version so they cannot drift.

## O veredito

Quer roteamento de alertas gratuito e self-hosted para Prometheus: Alertmanager. Quer escala de on-call, escalonamento e resposta a incidentes completos: PagerDuty. Eles combinam bem, com o Alertmanager roteando para o PagerDuty.

## FAQ

### Alertmanager vs PagerDuty: Which for Alerting?

Alertmanager handles deduplication, grouping, silencing, and routing of Prometheus alerts to receivers, but it is not a full on-call platform. PagerDuty adds on-call schedules, escalation policies, incident workflows, analytics, and integrations across hundreds of tools as a paid SaaS.

### Use case and scope?

Alertmanager suits teams wanting free, self-hosted alert routing tightly bound to Prometheus. PagerDuty suits organizations needing on-call rotations, escalation, incident workflows, and analytics. A common pattern routes Alertmanager alerts into PagerDuty for the human-response layer.

### Ops and CI fit?

Alertmanager is a small self-hosted binary you operate; PagerDuty is fully managed. Alertmanager config and routing rules are commonly validated in CI, where faster managed runners speed config tests and rule linting.

### Which should I choose?

Want free, self-hosted alert routing for Prometheus: Alertmanager. Want full on-call scheduling, escalation, and incident response: PagerDuty. They pair well, with Alertmanager routing into PagerDuty.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt