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. 02reconAlloy already present? service active?
3. 03reconexisting config to preserve?
4. 04reconLoki reachable from this server (200)?
5. 05reconPromtail still active (duplicate shipping)?
6. 06actAdd the Grafana repositoryverify
7. 07actInstall Grafana Alloyverify
8. 08actShip the systemd journal to Lokiverify
9. 09actEnable and startverify
10. 10actLogs reach Lokiverify

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 Grafana repositoryVerified byapt-cache policy alloy 2>/dev/null | grep -c Candidate || dnf info alloy -q | grep -c Version
2. 02verifyInstall Grafana AlloyVerified byalloy --version 2>&1 | head -1
3. 03verifyShip the systemd journal to LokiVerified byalloy fmt /etc/alloy/config.alloy >/dev/null && echo ok
4. 04verifyEnable and startVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:12345/-/ready
5. 05verifyLogs reach LokiVerified bycurl -s -G ${loki_url}/loki/api/v1/label/job/values | grep -c systemd-journal

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