Self-host Prometheus on a VPS
A metrics time-series database and alerting engine built for pull-based scraping.
levelrail-cli templates deploy prometheus --name my-prometheusSpecification
- Status
- Verified on arm64 with image tag v2.54.1
- Category
- Monitoring
- Services
- prometheus
- Ports
- 9090
- Volumes
- 1
- Memory
- about 512 MiB
- arm64
- tested
- amd64
- image published
- Settings to fill in
- none
- License
- Permissive license, Apache-2.0
About Prometheus
A metrics time-series database and alerting engine built for pull-based scraping. Runs as a single container from the prometheus image, listening on port 9090; data is kept in named volumes.
What it deploys
Prometheus runs as one service in a single Compose app, listening on port 9090, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| prometheus | prom/prometheus | v2.54.1 | 9090 | prometheus_data -> /prometheus |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Verified. Verified on arm64 with image tag v2.54.1. Verified means our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 9090 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
The catalog lists no environment variables for this template.
Install Prometheus on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get prometheus -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy prometheus --name my-prometheus
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Prometheus.
Docs and upstream
More in Monitoring
- PushgatewayA Prometheus Pushgateway that holds metrics pushed by short-lived batch jobs so a Prometheus server can scrape them. Pushed groups are kept on a persistent volume.
- PyroscopeA continuous profiling database with a web UI and a data volume. The UI has no login, so restrict access before exposing it. Applications push profiles to port 4040.
- OpenSpeedTestA browser speed test you host yourself. It measures download and upload speed between a visitor and this server, with no account and no stored results.
- OpenObserveA lightweight, single-binary observability platform for logs, metrics, and traces with a built-in UI.
- SmokePingA latency and packet loss monitor that pings your targets and graphs jitter over time. GPL-2.0 licensed. Targets live in the Targets file under the config volume. There is no login, so keep it private or behind an auth proxy.
- Speedtest TrackerRuns Ookla speed tests on a schedule and charts your connection's throughput, latency, and jitter over time.