I run uptime-kuma as part of my monitoring setup. This is the detailed operating note for why I use it, how I think about it, how it connects to the rest of the lab, and what I would check when it starts acting wrong.
Table of Contents
What this container does
Uptime Kuma watches services and tells me when something is down, slow, or returning the wrong response.
The container image is louislam/uptime-kuma:1. I document that on purpose because the image tells me where updates come from, what documentation to trust, and what project probably changed if the container starts behaving differently after an update.
Service screenshot
This screenshot is intentionally public-safe. I use cropped or login-level views and leave out tokens, private URLs, API keys, passwords, internal account details, and anything that would make the lab easier to attack.
Why I use Uptime Kuma
I use it because I do not want to discover outages by accident. Monitoring turns random surprises into visible events.
The deeper reason I use containers for this is control. I want every service to have a defined job, defined storage, defined network exposure, and a clear recovery path. If I cannot explain why a container exists, what data it owns, and what depends on it, then the stack becomes clutter instead of infrastructure.
How I set it up
- Run it as its own container.
- Persist monitoring data in a volume.
- Expose the web UI for admin access.
- Add monitors for public sites, internal ports, and key dashboards.
The setup pattern is always the same in spirit: the container should be disposable, but the data should not be. The app image can be pulled again. The configuration, media library, database state, workflow history, or uploaded files are the pieces that need to survive.
Docker Compose install shape
On Unraid, this maps to the same idea as the Docker template: pick the image, set the web UI port, map appdata for config, map the real data folders, then start the container. On Ubuntu or any normal Docker host, the same shape looks like this after replacing the placeholder paths with your own folders.
services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
restart: unless-stopped
ports:
- "3001:3001"
volumes:
- uptime-kuma-data:/app/data
I keep secrets out of public examples. Real passwords, VPN credentials, API keys, claim tokens, tunnel IDs, and private hostnames belong in environment files or the app UI, not in a public article.
How I use it day to day
- I use it as the first status page for the lab.
- I check history to separate a brief blip from a pattern.
- I use it to validate that important services are reachable after changes.
Day to day, I try not to treat Docker like a mystery box. I check the service from the app UI, then the container status, then logs, then storage and networking. That order keeps me from randomly restarting things when the real issue is a bad path, a dead dependency, or an expired token.
What it connects to
- HTTP monitors
- TCP port monitors
- ping checks
- notification providers
This matters because most container problems are not isolated. A media request app might be healthy but unable to reach Sonarr. Sonarr might be healthy but unable to reach a downloader. A web app might be healthy but failing because the database is gone. Mapping the connections makes troubleshooting faster.
How I would hook up notifications
- Configure Telegram, email, Discord, Slack, webhook, or n8n notifications.
- Use different urgency levels for public sites vs casual internal apps.
- Alert on repeated failures, not just every tiny transient blip.
My notification rule is simple: alert me when I need to act, not every time something makes noise. For public services, I care about uptime and response time. For automation services, I care about failed jobs and stuck queues. For sensitive services, I care about access, failed updates, and backup verification.
What I monitor
- monitor status
- notification delivery
- database volume
- container health
The minimum useful monitoring is container state plus one real application check. A container can be running while the app inside is broken, so I prefer checking the actual web endpoint, API health, or workflow behavior whenever possible.
What usually breaks first
- notification token expired
- wrong monitor URL
- DNS issue
- container down
When something breaks, I do not start by rebuilding the container. I first ask what changed: an image update, a config edit, a permission change, a moved folder, a full disk, a dead dependency, or an expired credential. Most Docker issues are boring once the dependencies are visible.
Backup and recovery notes
Back up the Uptime Kuma data volume because it contains monitor definitions and history.
For recovery, I care about tested restores. A backup that has never been restored is only a guess. The practical goal is to know which folder, volume, database, or config file has to come back first so the service can be rebuilt without panic.
Security notes
Protect the dashboard. Monitoring data can reveal internal service names and network shape.
I also avoid publishing secrets in these articles. Public notes can explain the architecture, the purpose, and the operating model without exposing passwords, tokens, private hostnames, tunnel IDs, or anything that gives someone a map to attack the setup.
Bottom line
Uptime Kuma earns a place in the lab when it solves a real problem and I can operate it without guessing. The point is not just having a container running. The point is knowing what it does, what depends on it, how I get notified, and how I recover it when something eventually breaks.
How I update it safely
I do not treat container updates like a blind button press. My safe update flow is: check the current container health, read what image is running, confirm backups or appdata are safe, update one service at a time when possible, then verify the web UI, logs, and any connected apps after the container comes back.
- Check whether the container is healthy before touching it.
- Back up appdata or confirm the backup path exists before risky upgrades.
- Update during a quiet window, especially for media and database-backed services.
- Verify the service after update with the UI, logs, and Uptime Kuma or a direct health check.
- If something breaks, roll back the image or restore appdata instead of guessing.