SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01recondistro (apt or dnf) and architecture (amd64/arm64)
2. 02reconnode_exporter already installed (upstream binary or distro package)? version?
3. 03reconservice already active or existing unit?
4. 04reconport 9100 free? otherwise which process holds it
5. 05recondedicated system user already exists?
6. 06actCreate the system userverify
7. 07actInstall the binary (latest release, checksum verified)verify
8. 08actsystemd serviceverify
9. 09actServes /metricsverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyCreate the system userVerified byid -u node_exporter
2. 02verifyInstall the binary (latest release, checksum verified)Verified by/usr/local/bin/node_exporter --version 2>&1 | head -1
3. 03verifysystemd serviceVerified bysystemctl is-active node_exporter
4. 04verifyServes /metricsVerified bycurl -s -o /dev/null -w '%{http_code}' http://${listen}/metrics

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

SEC.05

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.06

Deploy on Servor button

Maintain node_exporter or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.07

More observability recipes

1. 01NetdataNetdata real-time monitoring (stable channel), local dashboard on :19999.
2. 02PrometheusPrometheus (metrics collection), as a local systemd service on :9090.
3. 03GrafanaGrafana OSS (official repo), local on :3000, admin with a random password.
4. 04Grafana LokiLoki 3.7 log aggregation via Docker, local on :3100.
5. 05Grafana + Prometheus stackGrafana + Prometheus + node_exporter via Docker Compose, datasource preconfigured, all local.