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. 01reconDocker + Compose present?
2. 02reconports 3000/9090 free?
3. 03actWrite the stackverify
4. 04actStartverify
5. 05actGrafana respondsverify

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. 01verifyWrite the stackVerified bytest -f /opt/monitoring/docker-compose.yml && echo ok
2. 02verifyStartVerified bydocker compose -f /opt/monitoring/docker-compose.yml ps --status running -q | wc -l
3. 03verifyGrafana respondsVerified bycurl -sf -o /dev/null -w '%{http_code}' http://localhost:3000/api/health

SEC.03

Variables

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

SEC.04

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.05

More observability recipes

1. 01node_exporterPrometheus system metrics exporter, as a service.
2. 02NetdataNetdata real-time monitoring, on :19999.
3. 03PrometheusPrometheus (metrics collection), as a service on :9090.
4. 04GrafanaGrafana (dashboards), as a service on :3000.
5. 05Grafana LokiLoki log aggregation via Docker, on :3100.