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. 02reconPrometheus already installed (package or binary)? service active?
3. 03reconexisting config or data to preserve
4. 04reconport 9090 free? otherwise who holds it
5. 05reconlocal node_exporter to scrape (9100)? free disk for the TSDB
6. 06actUser and directoriesverify
7. 07actInstall the binaries (latest release, checksum verified)verify
8. 08actScrape config (only if missing)verify
9. 09actsystemd service (listens on 127.0.0.1:9090)verify
10. 10actResponds on :9090verify

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. 01verifyUser and directoriesVerified bystat -c '%U' /var/lib/prometheus
2. 02verifyInstall the binaries (latest release, checksum verified)Verified by/usr/local/bin/prometheus --version 2>&1 | head -1
3. 03verifyScrape config (only if missing)Verified by/usr/local/bin/promtool check config /etc/prometheus/prometheus.yml
4. 04verifysystemd service (listens on 127.0.0.1:9090)Verified bysystemctl is-active prometheus
5. 05verifyResponds on :9090Verified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:9090/-/ready

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 Prometheus 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. 01node_exporterPrometheus system metrics exporter, as a systemd service.
2. 02NetdataNetdata real-time monitoring (stable channel), local dashboard on :19999.
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.