Operations

Server Health

The scene we watch our own production with: a runbook, a rolling health log, and a daily probe. Needs no connected accounts: edit the runbook's endpoint table to point at your own systems.

What it needs

Nothing. No accounts to connect, no values to fill in. Push it and it runs.

What's in it

2 notes, and an agent that runs on a schedule.

Daily at 07:00 UTC Daily server health probe 0 7 * * *

The files

The structure is JSON; the content sits beside it as real files, referenced with $file.

server-health.blueprint.json
├── server-health/health-log.md
└── server-health/runbook.md

Served with every $file inlined at /blueprints/server-health.json. What's in a blueprint walks the format.

Push it

Straight from the URL. Nothing to clone.

daslab scene push https://daslab.run/blueprints/server-health.json

Push it again after editing and the same scene updates in place: ids resolve deterministically, so apply upserts rather than duplicates. The merge rules are on Export and import.