Install Node Exporter on your VPS
Infraa installs Prometheus Node Exporter on your VPS as a single pinned binary. It exposes host metrics — CPU, memory, disk, network, filesystems — on a /metrics endpoint bound to 127.0.0.1:9100, ready for Prometheus or VictoriaMetrics to scrape from the same server. The binary (1.11.1) is verified against a checked-in SHA-256 and runs as a dedicated non-root system user.
- Versions
- Node Exporter 1.11.1, 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 Node Exporter install do?
- Creates a dedicated, non-login system user (infraa-node-exporter) — the exporter never runs as root.
- Downloads the pinned node_exporter binary, verifying it against a SHA-256 checksum from the reviewed catalog before it's moved into place.
- Installs a systemd unit (infraa-node-exporter.service) that binds the /metrics endpoint to 127.0.0.1 on your chosen port (9100 by default).
- Enables and starts the service, then verifies it's listening.
How do I install Node Exporter with Infraa?
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.
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.
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 the exporter every 60 seconds — the service unit and the metrics port. Point the Prometheus or VictoriaMetrics module on the same server at 127.0.0.1:9100 and host metrics start flowing; nothing is exposed to the internet.
Node Exporter on Infraa — common questions
01What does Node Exporter actually collect?
Host-level metrics: CPU usage, memory, disk space and I/O, network traffic, and filesystem stats. It exposes them as a Prometheus /metrics endpoint that Prometheus or VictoriaMetrics scrapes on an interval — it stores nothing itself.
02Is the metrics endpoint public?
No. Infraa binds it to 127.0.0.1:9100, so only scrapers on the same server can read it. Host metrics can reveal a lot about a machine, which is why the module never listens publicly.
03Do I need Node Exporter if Infraa already monitors my server?
Infraa's own agent covers the monitoring basics — disk, memory, CPU, services. Node Exporter is for when you want the full Prometheus ecosystem: fine-grained series, PromQL queries, and Grafana dashboards you control.
Connect a server in 30 seconds, then install Node Exporter from the catalog or just ask in chat.
