I built this because I got tired of finding out my containers had crashed hours after the fact. Now I get a Telegram message the moment something goes wrong, and I can fix it from my phone without opening the Unraid web UI.

What It Does

The bot connects to your Docker socket and watches for events, container crashes, health check failures, OOM kills. When something happens, you get a Telegram alert with the relevant details (exit code, how long it was running, etc.) and buttons to take action immediately.

It also monitors your Unraid server itself via the GraphQL API, CPU temps, memory usage, array health, UPS status. If your CPU hits 80°C or a disk starts reporting SMART warnings, you'll know about it.

Beyond just reacting to problems, it actively watches container logs for errors. You configure which containers to watch and what patterns to look for (defaults to things like "error", "exception", "fatal"). When it spots something, you get an alert with the error message.

The AI Stuff

The AI features are optional, the bot works fine without them, you just won't have access to /diagnose or natural language queries.

Log Diagnosis (/diagnose)

When a container is misbehaving, you can run /diagnose plex and it'll grab the recent logs, send them to Claude, and get back an analysis of what's likely wrong and how to fix it. It's surprisingly good at recognizing common issues like database locks, permission problems, network timeouts, memory pressure.

Smart Ignore Patterns

Say you're getting spammed with alerts about some deprecation warning that's harmless. Instead of manually writing a regex to filter it, you hit the "Ignore Similar" button on the alert. The bot sends the error text to Claude (using the cheap Haiku model) and asks it to generate a regex pattern that'll match this error and similar variations of it. Then it adds that pattern to your ignore list.

Natural Language Chat

Instead of remembering commands, you can just ask questions: "Is anything crashing?", "Why is sonarr using so much memory?", "Show me the last errors from radarr". The bot figures out what you're asking for and runs the appropriate commands. If you've been talking about a specific container, it remembers context so you can say "restart it" after discussing plex and it knows what you mean.

You need an Anthropic API key for any of this. The cost is minimal, a few cents a month unless you're running diagnose constantly.

Alert Examples

🔴 CONTAINER CRASHED: radarr

Exit code: 137 (OOM killed)
Image: linuxserver/radarr:latest
Uptime: 2h 34m

[🔄 Restart] [📋 Logs] [🔮 Diagnose]
[🔕 Mute 1h] [🔕 Mute 24h]

The buttons actually work, tap Restart and it restarts the container. Tap Diagnose and it runs the AI analysis. Mute silences alerts for that container for the specified time (handy when you know something's broken and you're working on it).

Available in Community Apps - search "Unraid Monitor Bot". - Coming soon

Docker - https://hub.docker.com/r/dervish/unraidmonitorbot

Github - https://github.com/dervish666/UnraidMonitor

You'll need:

• Telegram Bot Token - Message https://t.me/BotFather, run /newbot, follow the prompts

• Your Telegram User ID - Message https://t.me/userinfobot, it'll tell you your numeric ID

Optional:

• Anthropic API Key - For AI features. Sign up at console.anthropic.com

• Unraid API Key - For server monitoring (CPU/temps/array). Generate one in Settings → Management Access

Configuration lives in /mnt/user/appdata/unraid-monitor/config/config.yaml. You can set which containers to watch for log errors, resource thresholds, protected containers that can't be controlled remotely, etc.

Common Commands

Command	What it does	/status
Shows all your containers and their state	/status plex	Details for one container (partial names work)
/resources	CPU/memory usage across containers	/logs radarr 50
Last 50 lines from radarr	/diagnose sonarr	AI analysis of sonarr's logs
/restart plex	Restarts plex (asks for confirmation)	/server
Unraid CPU, memory, temps	/array	Disk health, array status, parity
/mute plex 2h	No alerts from plex for 2 hours	/manage

This sounds really nice and useful, so, thanks

However, I get

PermissionError: [Errno 13] Permission denied: 'config/config.yaml'

Are permissions wrongly set? Must I create the yaml manually? It's not specified as such in the documentation (I think?)...

10 minutes ago, Krakout said:

This sounds really nice and useful, so, thanks

However, I get

PermissionError: [Errno 13] Permission denied: 'config/config.yaml'

Are permissions wrongly set? Must I create the yaml manually? It's not specified as such in the documentation (I think?)...

Go into the appdata share and give the "unraidmonitorbot" folder permissions. I ended up giving the data and config folder permissions too, but I'm not sure if that was necessary. Either way, fixed that same error for me.

17 minutes ago, stormfather said:

Go into the appdata share and give the "unraidmonitorbot" folder permissions. I ended up giving the data and config folder permissions too, but I'm not sure if that was necessary. Either way, fixed that same error for me.

Thanks for that. Which permissions did you give? For me both the parent folder and subfolders have 755.

Yes, sorry, I have updated the xml and docker with the correct permissions.

Just now, dervish said:

Yes, sorry, I have updated the xml and docker with the correct permissions.

ah great, thanks!

I have added a /setup command to help with configuration. If there is no config.yaml it will run a wizard to get you up and running quickly. You can also run the /setup command at any time to re-configure the container monitoring.

run it in the container console, I take it?

No, in the chat. it will walk you through setting up the server then list your docker containers and allow you to add them to the watched, killable, priority etc lists. If you already have the config it will allow you to adjust the settings.

You can type /help at any point in the chat to get a help page.

Edited February 10Feb 10 by dervish

Just now, dervish said:

No, in the chat. it will walk you through setting up the server then list your docker containers and allow you to add them to the watched, killable, priority etc lists. If you already have the config it will allow you to adjust the settings.

Oh that's awesome!

Waiting for the update to drop 😊

It's live, just force an update and it should update

What's new since launch (Feb 10 → v0.9.3)

Setup Wizard — First-run setup is now fully guided via Telegram. Auto-detects your Unraid server and classifies containers. Run /setup any time to reconfigure.

Multi-Provider AI — Now supports OpenAI and Ollama alongside Anthropic. Switch with /model. Works fine with no AI keys at all.

Inline Buttons Everywhere — Confirmations, diagnostics, ignore selection, and the manage dashboard all use tap-friendly buttons instead of text replies.

Multi-User Alerts — Alerts now go to all authorised users, not just the last active one.

New Alerts — Container recovery notifications, Docker health check alerts, restart loop detection (5+ crashes in 10 min), and mute expiry notifications.

/health Command — Bot version, uptime, monitor statuses, and Unraid connection at a glance.

Reliability — Unraid auto-reconnect, atomic config writes, log storm protection, thread safety fixes, graceful shutdown, and security hardening.

What's new since v0.9.3 (→ v0.17.0)
Been a busy few months — here are the headlines since the last update.
Manage Dashboard + Features Panel — /manage is now a full control panel: status, resources, server, disks, ignores and mutes, plus a ⚙️ Features section to switch features on and off right from Telegram — no config file editing.
Image-Update Alerts — opt-in daily check that tells you when a container has a newer image available, each with a one-tap Pull button.
Auto-Heal — opt-in: containers that report unhealthy get restarted automatically, with a storm guard that gives up (and says so) instead of looping forever. Protected containers are never touched.
Memory Pressure Management — when the server runs low on RAM the bot warns you and can stop low-priority containers to protect the important ones. The Stop buttons now show each container's RAM use, and you're told how much was freed after a kill.
Tune Alerts From the Buttons — server CPU temperature/usage and array capacity/disk-temperature alerts now carry Mute (1h/24h) and Adjust-Threshold buttons, and the new threshold sticks — no restart needed.
Smarter AI — choose a model family (sonnet/haiku/opus, auto-resolved to the latest) or a different model per feature (chat/diagnose/analyze); /diagnose now reads the container's full state and knows which alert fired, for much better root-cause answers; replies render bold and code properly; and the assistant will happily give you the status as a captain's log or a haiku — using real numbers.
Health in the Unraid Dashboard — the bot now reports healthy/unhealthy in docker ps and the Unraid UI via a built-in HEALTHCHECK — no port mapping needed.
Reliability — boot-time alerts are retried instead of lost if Telegram hiccups, explicit API timeouts so a slow model can't stall the bot, tests and dependency-CVE scanning run in CI on every change, plus a stack of security hardening.

Edited July 1Jul 1 by dervish