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.
- 01reconDocker Engine + compose plugin present and daemon active?
- 02reconAlertmanager already deployed? existing config in /opt/alertmanager?
- 03reconports 9093/9094 free?
- 04reconlocal Prometheus to connect (alerting block)?
- 05actInstall Docker Engine (only if missing)verify
- 06actMinimal config (only if missing)verify
- 07actStart Alertmanagerverify
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.
- 01verifyInstall Docker Engine (only if missing)Verified by
docker compose version && systemctl is-active docker - 02verifyMinimal config (only if missing)Verified by
docker run --rm -v /opt/alertmanager:/etc/alertmanager:ro --entrypoint amtool prom/alertmanager:v0.34.1 check-config /etc/alertmanager/alertmanager.yml - 03verifyStart AlertmanagerVerified by
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:9093/-/healthy
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never put receiver secrets (Slack/PagerDuty webhook) in clear text in logs or in a displayed command. Never overwrite an existing alertmanager.yml. No auth: stay on 127.0.0.1.
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.
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.05
Deploy on Servor button
Maintain Alertmanager 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
- 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.
- 04GrafanaGrafana OSS (official repo), local on :3000, admin with a random password.
- 05Grafana LokiLoki 3.7 log aggregation via Docker, local on :3100.
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.