# Prometheus Alertmanager

Prometheus Alertmanager is the alert routing component for Prometheus, deduplicating, grouping, silencing, and forwarding alerts to email, PagerDuty, OpsGenie, or webhook receivers. It is open source and self-hosted, installable on Docker Hub, Kubernetes (Helm), Proxmox and Unraid.

Canonical page: https://ourlocalhost.com/app/3783/prometheus-alertmanager

## Description

Prometheus Alertmanager is the alert routing component for Prometheus, deduplicating, grouping, silencing, and forwarding alerts to email, PagerDuty, OpsGenie, or webhook receivers.

## Platform availability

Available on 3 of 10 platforms: Unraid, Proxmox, Helm.

## Health score

80/100 (Excellent), based on 4 of 5 factors.
- Maintained: 100 (last commit 7 days ago)
- Popular: 79 (8,699 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Security check: 86 (no serious findings, CI, tests, OpenSSF Scorecard 6.6/10)

## Links

- Docker Hub: https://hub.docker.com/r/ubuntu/prometheus-alertmanager
- Kubernetes (Helm): https://artifacthub.io/packages/helm/prometheus-community/alertmanager
- Documentation: https://prometheus.io/docs/alerting/alertmanager/
- Proxmox: https://community-scripts.github.io/ProxmoxVE/scripts?id=prometheus-alertmanager
- Official website: https://prometheus.io/
- GitHub: https://github.com/prometheus/alertmanager
- Unraid: https://ca.unraid.net/apps/prom-alertmanager-0vyvpu716lf48j?q=prom-alertmanager

## Common questions

### What port does the example Docker deployment expose for Alertmanager?

The example maps container port 9093 to 127.0.0.1:9093. This makes Alertmanager reachable at localhost:9093.

### What must the root route contain in an Alertmanager configuration?

The root route must not have matchers and must have a receiver configured. That receiver handles alerts that do not match any sub-route.

### Why might Prometheus not send alerts to Alertmanager even though alerts are visible in Grafana?

The Prometheus-to-Alertmanager connection may be failing, and that failure can be hard to see when alerts still appear in Grafana. Debugging the connection is the next step.

### Can I use a self-hosted Alertmanager with an existing cloud Prometheus setup?

Yes, a self-hosted Alertmanager can manage alerts while leaving existing cloud Prometheus dashboards unchanged. One described approach uses an infrastructure-as-code deployment.

### Can Alertmanager be considered for replacing alerts from Icinga2 or Zabbix?

A user evaluated migrating alerts from Icinga2, Zabbix, and custom plugins to Prometheus Alertmanager. That user reported receiving a lot of positive feedback.

## Alternatives

- Better Stack: AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
- Datadog: Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
- HyperDX: An open source observability platform: Unify session replays, logs, traces, and errors – all without the Datadog price tag.
- New Relic: Pinpoint and solve performance issues in your Ruby, Java, .NET, PHP and Python apps with real user, application and server monitoring.
- Splunk: Splunk is a self-hosted platform for collecting, indexing, searching, and analyzing log and security data, helping homelabbers and operatio…

---
Source: Our Local Host (https://ourlocalhost.com/app/3783/prometheus-alertmanager), the self-hosted and open-source app directory.
