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.
- 01recondistro (apt or dnf) and architecture (amd64/arm64)
- 02reconGrafana already installed? version?
- 03reconservice active? existing config and database to preserve
- 04reconport 3000 free? otherwise who holds it
- 05reconreverse proxy present (only useful if a domain is provided)
- 06actAdd the Grafana repositoryverify
- 07actInstall Grafanaverify
- 08actListen on 127.0.0.1verify
- 09actEnable and startverify
- 10actRandom admin password (fresh install)verify
- 11actTLS 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.
- 01verifyAdd the Grafana repositoryVerified by
apt-cache policy grafana 2>/dev/null | grep -c Candidate || dnf info grafana -q | grep -c Version - 02verifyInstall GrafanaVerified by
(dpkg -s grafana 2>/dev/null || rpm -qi grafana) | grep -m1 -i "^version" - 03verifyListen on 127.0.0.1Verified by
grep -E '^http_addr' /etc/grafana/grafana.ini - 04verifyEnable and startVerified by
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:3000/api/health - 05verifyRandom admin password (fresh install)Verified by
curl -s -o /dev/null -w '%{http_code}' -u "$(cat /root/grafana-admin.txt)" http://127.0.0.1:3000/api/user - 06verifyTLS reverse proxy (only if a domain is provided)Verified by
curl -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.
Never reset the admin password of an existing Grafana. Do not touch /var/lib/grafana/grafana.db. Grafana stays on 127.0.0.1 unless behind a TLS reverse proxy. Say where /root/grafana-admin.txt is.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${domain} | Domain (optional) |
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Grafana 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
- 01node_exporterPrometheus system metrics exporter, as a systemd service.
- 02NetdataNetdata real-time monitoring (stable channel), local dashboard on :19999.
- 03PrometheusPrometheus (metrics collection), as a local systemd service on :9090.
- 04Grafana LokiLoki 3.7 log aggregation via Docker, local on :3100.
- 05Grafana + Prometheus stackGrafana + Prometheus + node_exporter via Docker Compose, datasource preconfigured, all local.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.