Lavalink Node Monitoring
Lavalink node monitoring polls the /v4/stats endpoint — players, playing streams, memory and CPU load — so a wedged or OOM-ing audio node pages you instead of quietly dropping every voice session.
Your music bot goes silent mid-queue — Lavalink's REST stats tell you before the Discord server does
What it checks
- REST API reachability and auth on /v4/stats
- Player and playing-stream counts per check
- Memory usage and Lavalink/system CPU load metrics
Set it up
- 1Add a Lavalink monitor with the node host and port (default 2333)
- 2Set the REST password from application.yml — sent as the Authorization header
- 3Alert when the node stops answering stats or auth fails
FAQ
Why not just check if the port is open?
A Lavalink node can hold the TCP port while its audio pipeline is dead or the password rotated. Polling /v4/stats proves the REST layer answers and returns real player/load metrics.
Is the password stored safely?
It lives in the monitor's encrypted settings and is only used as the Authorization header for the stats request — the same credential Lavalink clients already need.
Which Lavalink version does this need?
Lavalink v4 exposes /v4/stats with players, playingPlayers, uptime, memory and cpu. Older v3 nodes expose /stats — use an HTTP check on that path instead.
Related check types
Start monitoring in minutes
External probes plus internal agents, escalation chains and status pages — free tier, no card required.