Menu

1 / 2

Uptime Kuma had never added a monitor on its own, so I wrote kuma-discover

DEV Community: github·Christian Anderson·about 14 hours ago
#Vt23FBlD
#devtogithub#technology#devto#dev#kuma
Reading 0:00
15s threshold

On 7 October I moved Uptime Kuma onto my ZimaBlade. While I was repointing everything at it, I noticed something a bit embarrassing: nothing had ever added a monitor automatically. Kuma watched exactly what I'd remembered to click into it, and nothing else. Every new container was unwatched until I happened to think of it.

So I wrote a small script that compares what's actually running with what Kuma is watching. Its first run found 18 services and 5 gaps . I approved all 5. Today I've cleaned it up and published it as kuma-discover .

What it does

Looks at your Docker hosts over SSH for containers with a published port. Loopback-only ports don't count, because Kuma can't reach them anyway.

Optionally looks at Proxmox LXC containers and your Cloudflare Tunnel hostnames.

Works out what's already covered: same IP, same host and port, same hostname, a watched tunnel hostname in front of it, or a monitor with the same name.

Asks before adding anything.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.