Monitoring

Install VictoriaMetrics on your VPS

Infraa installs VictoriaMetrics on your VPS as a single Go binary — a fast, low-resource time-series database that accepts Prometheus remote-write and answers PromQL-compatible queries, with the vmui web interface built in. The binary (1.147.0) is pinned and verified against a checked-in SHA-256, runs as a dedicated non-root system user, and binds to localhost on port 8428.

Versions
VictoriaMetrics 1.147.0, a pinned single-binary release verified by SHA-256
Works on
Ubuntu 22.04, Ubuntu 24.04, and Debian 12
Package source
Pinned binary release

What does the VictoriaMetrics install do?

  • Creates a dedicated, non-login system user (infraa-victoriametrics) — it never runs as root.
  • Downloads the pinned VictoriaMetrics binary, verifying it against a SHA-256 checksum from the reviewed catalog before it's moved into place.
  • Installs a systemd unit (infraa-victoriametrics.service) that binds the HTTP API — ingest, PromQL, and vmui — to 127.0.0.1:8428, with time-series data in /var/lib/infraa-victoriametrics.
  • Enables and starts the service, then verifies it's listening.

How do I install VictoriaMetrics with Infraa?

  1. Connect your server

    Run the Infraa install one-liner (curl install.infraa.sh | sh) on your VPS. The agent registers over an outbound connection in about 30 seconds — no inbound ports, no SSH keys to share.

  2. Pick the service

    Choose it from the one-click catalog in the dashboard, or just ask in chat. Infraa turns your request into a concrete, reviewable plan.

  3. Review and approve

    Read exactly what will run, then approve. The agent executes only the approved, cryptographically signed steps and streams progress live.

What happens after the install?

Infraa checks VictoriaMetrics every 60 seconds — the service unit and port 8428. Pair it with the Node Exporter module for host metrics and Grafana for dashboards, all on the same server; everything speaks to 127.0.0.1, nothing is exposed.

VictoriaMetrics on Infraa — common questions

01

Does VictoriaMetrics replace Prometheus?

It can. VictoriaMetrics accepts Prometheus remote-write, scrapes targets, and answers PromQL-compatible queries while using considerably less memory and disk — a good fit for a single VPS. Grafana connects to it like it would to Prometheus.

02

How much server does VictoriaMetrics need?

Very little — the module's floor is 256 MB of memory and 5 GB of disk. VictoriaMetrics is designed to be low-resource, which is why Infraa offers it alongside Prometheus for smaller servers.

03

Where is the metrics data stored?

In /var/lib/infraa-victoriametrics, owned by the dedicated system user. Data survives restarts and upgrades — re-installing replaces the pinned binary without touching the time-series store.

Connect a server in 30 seconds, then install VictoriaMetrics from the catalog or just ask in chat.