Skip to main content
This guide walks through installing Alertmanager, starting the service, and configuring Prometheus to send alerts to it. The steps assume a Linux host with wget and tar available.

Download Alertmanager

  1. Open the Prometheus downloads page and locate the Alertmanager section to copy the direct URL for the binary you need:
  2. On the Alertmanager server, download and extract the archive:
  1. Inspect the extracted files:
The image displays a download page for Prometheus, showing downloadable files for different components like Prometheus, Alertmanager, and Blackbox Exporter, with details such as version, operating system, architecture, and file size.
You can run Alertmanager from the extracted folder. By default it looks for alertmanager.yml in the current working directory and stores runtime state under data/. Use --config.file and --storage.path to override these locations.

Start Alertmanager

From the extracted directory, start Alertmanager:
You should see logs similar to this, indicating successful startup and the listening address:
By default Alertmanager listens on port 9093. Open a browser to http://localhost:9093/ (or replace localhost with the server IP) to access the Alertmanager web UI.
If exposing Alertmanager to the public internet, secure the interface with a reverse proxy and TLS, or restrict access via firewall rules. Alertmanager can contain sensitive routing and receiver details.

Configure Prometheus to Use Alertmanager

After Alertmanager is running, add it to your Prometheus configuration under the alerting section. Below is an example prometheus.yml snippet showing how to point Prometheus to one or more Alertmanager instances:
  • Replace alertmanager1 / alertmanager2 with hostnames or IP addresses reachable from your Prometheus server.
  • Prometheus sends alerts to these targets via the Alertmanager API on port 9093.

Quick Troubleshooting

  • If logs show “gossip not settled”, this is expected for clustered Alertmanager nodes until they discover each other.
  • If Prometheus can’t reach Alertmanager, confirm network reachability and that Alertmanager is listening on port 9093 (ss -lntp | grep 9093).
  • Use amtool for local inspection and to manage silences from the command line.

References

Watch Video