An alert rule can tell a webhook, Slack or Discord when it fires and when it's resolved. Until now a webhook alert was signed only when you had set a secret, and if your app missed it, it was gone.
Now every webhook alert is signed, tried again until your app takes it, and kept in order. Above is a webhook channel with the signing secret ngris made for it, and the page that shows that secret once, right after you save.

What changed
- Always signed. Each webhook channel has a signing secret, a
whsec_key. Leave it empty and ngris makes one and shows it once. Every alert carries the Standard Webhooks headers, so a ready library in your language checks it, andX-Ngris-Signatureas before. - Checkable behind ngris. If your app runs behind ngris, check the Standard Webhooks headers: they reach it as sent.
- Tried again. An alert your app doesn't answer with a
2xxis sent again for about 51 minutes, 6 tries, with the samewebhook-idso your app can drop a repeat. A429answer'sRetry-Afteris honoured. - In order. A channel's alerts arrive in the order they happened: a resolved never overtakes its firing. Slack and Discord get the same retries and order.
- A test that means it. Send test passes only on what a real alert needs: a
2xxanswer, no redirect followed. - At most a day late. An alert still not delivered 24 hours after it happened is dropped, and the rule's history says why.
Get started
- Open Alerts and create a rule, or edit one.
- Add a Webhook channel with your app's
https://address. ngris fills in a signing secret: copy it into your app. - Read the docs: Webhook delivery and Webhook signatures.
