warden / where to reach you
Where to reach you.
Warden works alone until the decision is yours. It posts to every address here when something breaks, when it stops to ask you, and when it acted and the check still fails — and, for addresses set to everything, when it fixed something and proved it. A Slack or Discord incoming webhook is exactly this, and so is anything you write yourself: a POST with JSON, and no credential of yours is stored beyond the URL.
Addresses
What gets sent
- something brokeA check failed twice in a row, so this is an outage rather than a blip. Warden is already looking into it.
- needs youWarden worked out what to do and your rules say the decision is yours. The run is held open until you answer.
- acted, and it is still downIt did what it was allowed to do and the check it re-ran still fails. It will not call that fixed.
- handed backIt could not find a cause, or nothing it was allowed to do would help.
- fixedOnly to addresses set to everything. Something broke, Warden fixed it, and the check that failed passes again — so you read about it in the morning instead of at 3am.
The payload carries the service, the title, the body and a link, plus a text field that Slack renders and a content field that Discord renders — so one address shape reaches both without Warden knowing which is which.
You have nothing of your own registered yet, so there is nothing to be woken about. Point Warden at something first.