Packages / prometheus-alertmanager

APT repository · deb.freshdeb.com/prometheus-alertmanagerprinted 28 Oct 2026, 07:45 UTC

prometheus-alertmanager

Prometheus Alertmanager routes, groups and silences alerts. Built like upstream's release, with the web UI. One release line for Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04 on amd64 and arm64.

latest 0.34.1github.com/prometheus/alertmanager upstream source packaging

Componentmain

follows every upstream release, minors and majors included. Currently 0.34.1.

Release line

Deliver to

prometheus-alertmanager 0.34.1-4+freshdeb~deb13

1Trust the signing key (once per machine)

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://deb.freshdeb.com/freshdeb-archive-keyring.gpg \
  | sudo tee /etc/apt/keyrings/freshdeb-archive-keyring.gpg >/dev/null

Fingerprint 3BBD F03A 9C0B F890 F8CA 9510 7595 CC55 468F 3161. How to verify.

2Add the source

sudo tee /etc/apt/sources.list.d/freshdeb-prometheus-alertmanager.sources >/dev/null <<EOF
Types: deb
URIs: https://deb.freshdeb.com/prometheus-alertmanager
Suites: $(. /etc/os-release && echo $VERSION_CODENAME)
Components: main
Signed-By: /etc/apt/keyrings/freshdeb-archive-keyring.gpg
EOF

With auto, the shell reads the codename from /etc/os-release on the machine you paste this into.

3Install

sudo apt update && sudo apt install prometheus-alertmanager
apt policy prometheus-alertmanager   # expect 0.34.1-4+freshdeb~…

Before you upgrade from the distribution's prometheus-alertmanager

The freshdeb version sorts higher, so apt upgrade moves you over in place. 0.27 removed the v1 API: anything still calling /api/v1 has to move to /api/v2. The package's NEWS entry lists the other changes.

prometheus-alertmanager 0.34.1-4+freshdeb~deb13

Compared with Debian's package

Debian's packaging decides where things go: package names, paths, users, services and how upgrades behave. The build follows upstream's own release builds wherever Debian's differs.

Web UI: Included, from upstream's release (pinned by sha256). Debian can't build it, because it needs an Elm toolchain, so its package has none.
Features: The Kafka output for the event recorder, which Debian's build leaves out.
Build: Pinned Go toolchain, CGO_ENABLED=0, tag netgo, upstream's version stamps. Upstream's tests, including the acceptance tests, gate the build.
Layout: Debian's: /etc/prometheus/alertmanager.yml, data in /var/lib/prometheus/alertmanager, amtool, systemd unit and init script. --web.ui-path from Debian's packages is accepted and ignored.

Packing list

Every release line of prometheus-alertmanager and the distributions it's built for. Each line is its own APT component and only gets the releases it follows (main: every upstream release, minors and majors included). After upstream end of life it stops building but stays installable. Hatched cells have no build: usually that distribution already ships the same or a newer version itself.

Line	Component	Current	bookwormDebian 12	trixieDebian 13	jammyUbuntu 22.04	nobleUbuntu 24.04	resoluteUbuntu 26.04	Support
main	main	0.34.1	built: 0.34.1-4	built: 0.34.1-4	built: 0.34.1-4	built: 0.34.1-4	built: 0.34.1-4	–

Versions follow <upstream>-<revision>+freshdeb~<distro>, distro being deb12, deb13, ubuntu22.04, ubuntu24.04 or ubuntu26.04, for amd64 and arm64. Published versions are never rebuilt or replaced.

prometheus-alertmanager: handle and deliver alerts created by Prometheus

Origin

Upstream: github.com/prometheus/alertmanagerrelease tags pinned to commit hashes
Debian packaging: salsa.debian.org/go-team/packages/prometheus-alertmanagerimported unmodified at 7a0e028 (0.33.1-5, unstable)
Our changes: Per-line quilt patches under patches/, plus overlays under overlays/ for bookworm, trixie, jammy, noble, resolute.
Built for: bookworm, trixie, jammy, noble, resoluteamd64, arm64, built natively
Notes: packaging notes · package.yaml · report an issue

Also in Prometheus

All 23 packages