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. 02reconDocker Engine + compose plugin present and daemon active?
3. 03reconstack already written in /opt/monitoring? do not overwrite
4. 04reconports 3000/9090/9100 free? otherwise who holds them
5. 05reconat least 1 GB of RAM; reverse proxy present (if domain)
6. 06actInstall Docker Engine (only if missing)verify
7. 07actWrite the Prometheus config and the Grafana datasourceverify
8. 08actGenerate the Grafana admin passwordverify
9. 09actWrite the stackverify
10. 10actStartverify
11. 11actGrafana and Prometheus respondverify
12. 12actTLS reverse proxy (only if a domain is provided)verify

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. 01verifyInstall Docker Engine (only if missing)Verified bydocker compose version && systemctl is-active docker
2. 02verifyWrite the Prometheus config and the Grafana datasourceVerified byls /opt/monitoring/prometheus.yml /opt/monitoring/grafana/provisioning/datasources/prometheus.yaml
3. 03verifyGenerate the Grafana admin passwordVerified bystat -c '%a' /opt/monitoring/.env && grep -c GF_SECURITY_ADMIN_PASSWORD /opt/monitoring/.env
4. 04verifyWrite the stackVerified bydocker compose -f /opt/monitoring/compose.yaml config -q && echo ok
5. 05verifyStartVerified bydocker compose -f /opt/monitoring/compose.yaml ps --status running -q | wc -l
6. 06verifyGrafana and Prometheus respondVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:3000/api/health
7. 07verifyTLS reverse proxy (only if a domain is provided)Verified bycurl -s -o /dev/null -w '%{http_code}' https://${domain}/api/health

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 Grafana + Prometheus stack 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. 03PrometheusPrometheus (metrics collection), as a local systemd service on :9090.
4. 04GrafanaGrafana OSS (official repo), local on :3000, admin with a random password.
5. 05Grafana LokiLoki 3.7 log aggregation via Docker, local on :3100.