Relay - Crash, Backup & Resource Alerts on Discord

Relay tells you when a server needs you, in the place you already are. Crashes, backups, resource spikes and the console lines you actually care about arrive in Discord as clean embeds — through webhooks alone. No bot to host, no token to store, nothing for your customers to authorise.

DEMO: http://5.10.220.249/auth/login test@test.com test1234

The part that matters: it keeps watching when nobody is looking. A scheduled worker polls every server on its own, so a 4am crash reaches Discord even though no one has the panel open. And it knows a crash from a shutdown — when a server goes offline, Relay checks the panel’s own activity log first, so pressing Stop stays silent while a real crash does not.

WHAT GETS SENT

• Power state — the server started, or someone stopped it
• Crashes — a running server went offline and nobody asked it to
• Backups — completed or failed, with the backup name
• Resource thresholds — CPU, memory or disk crossed the limit, with an optional “back to normal” notice when it recovers
• Console keywords — a console line contained one of the words that server’s owner watches for: OutOfMemoryError, “Can’t keep up”, a crash signature specific to their modpack

WHAT THE SERVER OWNER CONTROLS

• Their own webhook, per server, stored masked and never handed back to the browser in full
• Which of the five event types they want
• Their own console watch-words, one per line
• Per-event channel routing: crashes to #alerts, backups to #backups, everything else to the main channel
• A “Send test message” button, so they can confirm it works before they need it to

WHAT YOU CONTROL FROM ADMIN

• Master switch: every notification on the panel off in one click
• A fallback webhook for servers whose owners never set one
• Whether owners may set a webhook at all, and whether they may route per event
• Each of the five event types, on or off panel-wide
• CPU / memory / disk thresholds, and the recovery notice
• Console limits: how many words a server may watch (1–25), how much console to read (4 KB – 128 KB), and how long before the same match repeats (1 minute – 24 hours)
• Poll interval, 30 to 900 seconds — ease it off on a busy panel
• Embed styling: title, footer, webhook username and accent colour
• Rate limit per event type, 1 to 120 minutes, so a flapping server cannot flood a channel
• Mentions: off by default, and never allowed in text that came from a game console

**SUPPORT: https://t.me/whoisfazil

• Fully supported. Missing something, or have an idea for it? Tell me — feature requests are welcome. Run into a problem? Message me on Telegram and I will get you a fix.

• Rate the product however you see fit, but if something is broken please tell me about it directly too — a review alone does not tell me what went wrong on your setup, and I cannot fix what I do not know about.**

Requires Pterodactyl with Blueprint, and the panel scheduler running for background delivery.