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. 02reconVector already present? service active?
3. 03reconexisting config (vector.yaml/toml)? is it the package demo config?
4. 04reconports 8686 (API) and 9598 (exporter) free?
5. 05actAdd the Vector repositoryverify
6. 06actInstall Vectorverify
7. 07actBase config (only if missing or demo)verify
8. 08actEnable and startverify

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. 01verifyAdd the Vector repositoryVerified byls /etc/apt/sources.list.d/ /etc/yum.repos.d/ 2>/dev/null | grep -ci vector
2. 02verifyInstall VectorVerified byvector --version
3. 03verifyBase config (only if missing or demo)Verified byvector validate --no-environment /etc/vector/vector.yaml
4. 04verifyEnable and startVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8686/health

SEC.03

Guardrails

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

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

Deploy on Servor button

Maintain Vector 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.06

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.