Self-host Alertmanager with Levelrail
VerifiedPrometheus Alertmanager: groups, deduplicates and routes alerts to email, Slack, webhooks and on-call tools.
- Authorprometheus
- LicenceApache-2.0
- Memory128 MiB
- Archarm64
- Services1
How to self-host Alertmanager
-
Pull the images
One image is pulled on your server.
Show images
prom/alertmanager:v0.27.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 9093.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Alertmanager requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 9093
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Verified. Verified on arm64 with image tag v0.27.0. Our CI ran this exact image version and it answered on its health path. Evidence
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Alertmanager. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Alertmanager docs page.
Deploy Alertmanager your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Alertmanager from the CLI
levelrail-cli templates deploy alertmanager --name my-alertmanager Deploy Alertmanager with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/alertmanager/deploy Alertmanager configuration
Alertmanager services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| alertmanager | prom/alertmanager:v0.27.0 | 9093 | data -> /alertmanager |
Alertmanager environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 9093
- Volumes
- 1 named mount: data -> /alertmanager
Alertmanager FAQ
How much memory does Alertmanager need?
The catalog lists about 128 MiB of memory for Alertmanager.
Does Alertmanager run on arm64?
For Alertmanager, arm64 is tested; amd64 is image published.
What licence is Alertmanager under?
Alertmanager is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Alertmanager need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Alertmanager use?
Alertmanager listens on port 9093 inside the stack.
Where does Alertmanager keep its data?
In a named volume: data mounted at /alertmanager.
Can I deploy Alertmanager on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Alertmanager, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image prom/alertmanager:v0.27.0 is what you deploy there.