Rust Server Crash Alerts
Know your server is down before your players tell you.
Panelra watches every Rust server you run and alerts you when one crashes, keeps crashing, stops responding, gets stuck while starting, or when its host goes offline. Alerts land in the panel and in your Discord channel.
Alerts That Mean Downtime
Crash, crash loop, hung server, stuck while starting and host offline. Each alert is about a server your players cannot use right now.
Alerts Inbox
Every open alert for your team in one place in the panel, with the server, what happened and when. Alerts close on their own when the problem is gone.
Discord Webhook
Send alerts to a Discord channel with a webhook. Pick which events each webhook posts, so the admin channel gets crashes and the public channel does not.
Crash detection and crash history
When the Rust server process exits unexpectedly, the agent on your host notices right away and reports it. Panelra raises a crash alert and adds an entry to that server's crash history: when it happened, the exit reason, whether the process ran out of memory, and the last lines of the server log before it went down. Crash history is kept for 30 days, so you can see whether a crash was a one-off or the third one this week, and which plugin was printing errors just before.
Crash loop detection
A single crash is often followed by an automatic restart and the server comes back on its own. A crash loop is different: a bad plugin, a broken config or a failed update makes the server crash again every time it starts. Panelra flags a crash loop when a server crashes 3 times within 15 minutes, so you get one clear alert that says "this server keeps crashing and restarting" instead of a stream of separate crash messages.
Hung server and stuck while starting
Some failures do not end the process. A server can freeze with the process still alive, or sit in the loading stage and never finish starting. Panelra checks that a running server still answers RCON and raises a Not responding alert when it stops. A separate alert covers a server that started but never became ready. In both cases the panel offers a force restart, which stops the process and starts it again without waiting for a save the frozen server cannot do.
Host and agent offline
If the machine goes down, loses its network or the agent stops, Panelra loses contact with every server on it. Once the host has been offline for about 3 minutes a Host offline alert is raised, and it clears when the agent connects again. Short network blips do not trigger it, so you are not woken up for a reconnect that fixed itself.
Discord alerts per server
Add a Discord webhook to a server and choose what it posts: crashes, not responding, host offline, F7 player reports, and optionally restarts, wipes, backups and plugin updates. You can post failures even when you turn the routine events off. Each server can have its own webhooks, so a staff channel can get every alert while your community channel only hears about wipes.
What Panelra does not alert on
Panelra does not send alerts for CPU or RAM usage thresholds. Host resource usage is shown on the dashboard, but alerts are kept for events where a server is actually down or unusable, so every alert is worth reading. If you want fewer out-of-memory crashes in the first place, a daily restart schedule is the usual fix.
Alert types at a glance
| Alert | When it fires |
|---|---|
| Crash | The Rust server process exited when it should have been running. |
| Crash loop | The server keeps crashing and restarting: 3 crashes within 15 minutes. |
| Not responding | The process is running but the server stopped answering RCON, usually a hang or a freeze. |
| Stuck while starting | The server started but never finished loading and never became playable. |
| Host offline | The host has been offline for about 3 minutes, so every server on it is out of reach. |