Uplance Monitor types Discord bot
Monitor whether your Discord bot is online
Uplance checks presence the way Discord itself reports it, through a real gateway connection — not by asking your host whether the process is alive.
Free for 10 monitors · no credit card
The problem
Your bot's process is running, its logs are quiet, its container is healthy — and it has been showing as offline for six hours because the gateway connection dropped and never reconnected.
This is the most common way a bot fails, and it is invisible to every check that looks at the host instead of at Discord.
What the check looks at
Presence
Whether Discord reports the bot as online, through the workspace bot's own gateway connection.
Reconnect loops
Repeated flips between online and offline raise one flapping alert instead of forty.
Command health
Pair it with a heartbeat from inside your command handler to prove the bot is responding, not just connected.
Call a heartbeat from inside your command handler
// after a command is handled successfully
await fetch("https://uplance.cloud/api/push/<token>?msg=commands%20ok");And the alert actually arrives
Most monitoring tools are fine until the one time the alert doesn't arrive. Uplance is built so that can't happen quietly.
- Every alert is written to an outbox before it is sent, and retried for about fifty minutes. A restart doesn't lose it.
- Once a week, a real test event is sent through every channel you've configured, and you're told which ones failed.
- If the alert pipeline is in trouble, the dashboard says so — it isn't buried in a log file.
- If the checker itself stops, the health endpoint returns 503 so an outside heartbeat can page you, and your status page says monitoring has stopped instead of showing stale green.
Common questions
- Why not just check if the process is running?
- Because that is exactly the check that passes while the bot is offline. The process is fine; the gateway connection is what broke. Presence is the only thing that answers the question your users are asking.
- Do I have to give you my bot token?
- No. Presence is observed through the workspace's own Discord bot, which you invite to your server. Credentials that a monitor does need — database passwords, for instance — are encrypted at rest with AES-256-GCM.
- Can the alert go to the same Discord the bot is in?
- Yes, and it should. Alerts arrive with I'm on it, Mute 1 h and Resolve buttons, so whoever is around handles the incident without leaving the app.
Also monitored
Know it's down before your customers do.
10 monitors, 30 days of history, no credit card