Prometheus Alertmanager
Prometheus Alertmanager is the alert routing component for Prometheus, deduplicating, grouping, silencing, and forwarding alerts to email, PagerDuty,…
Platform availability
Available on 3 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
80/100 Excellent
- Maintained
- 100last commit 7 days ago
- Popular
- 798,699 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 86no serious findings, CI, tests, OpenSSF Scorecard 6.6/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 12 days ago
- GitHub stars
- 8,699
- Open issues
- 422
- Last commit
- 2026-11-14
- Latest release
- v0.35.0
- License
- Apache-2.0
- Activity
- declining
Checked 5 days ago - source: GitHub (prometheus/alertmanager)
Resources & Compatibility
Minimum requirements: 1 CPU core(s). ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Keep Prometheus reachable on port 9090 Make sure port 9090 is open on the host so you can reach the Prometheus API and dashboard with curl or a browser. If it is blocked, you cannot check targets, query metrics, or manage the app from the web interface. source
- Use the global YAML as a config template Use the provided global YAML block as a starting point when editing your Prometheus config, and keep a backup before changing it. Changing timings such as scrape_interval, scrape_timeout, or evaluation_interval incorrectly can prevent Prometheus from reloading or stop it from collecting metrics. source
- Start demo exporters on ports 8080-8082 If you are following the getting-started example, start Node Exporter on ports 8080, 8081, and 8082 in separate terminals. Prometheus needs to reach those /metrics endpoints to collect the demo data; without them, the example targets will not appear. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (5)
- 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…
Checked 54 days ago - source: AlternativeTo
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.
Answers sourced from community.grafana.com, discuss.prometheus.io, github.com, www.reddit.com
Community
- What do you use for alerting? : r/selfhosted - Reddit (reddit)
- Options for running self-hosted AlertManager with cloud Prometheus (other)
- Prometheus Alertmanager : r/devops - Reddit (reddit)
- Unable to debug prometheus to alertmanager connection (forum)
- How to set alertmanager in prometheus-community/prometheus helm chart ... (forum)
- Reddit (reddit)
Collected 48 days ago - public community threads