Uptime Kuma's monitors, in Tillarr.
Uptime Kuma watches everything else; Tillarr watches Uptime Kuma. The first beta checks it by address. During the beta, Tillarr reads which monitors are up and down, and at 1.0 Kuma can notify you through Tillarr.
What you see
- Whether it answers, how quickly, and which address answered
- A tap to open its own web page
What's next
During the beta: monitors up and down, read with its metrics key. With Pro, a guided setup points Uptime Kuma's ntfy notification at Tillarr.
Connect Uptime Kuma
What to have ready when you add it in Tillarr.
- Its address. Usually http://your-server:3001. Add a remote address too, and Tillarr uses it when home doesn't answer.
- Nothing else. Watching needs no key and no login, so it's free and can't change anything in Uptime Kuma. When full support arrives, Tillarr asks for its key.
Good to know
- Uptime Kuma's only official API is its metrics endpoint, so that's what Tillarr reads.
Behind a sign-in page
If a sign-in page guards Uptime Kuma, let /dashboard through so the check can reach it. The remote access guide shows how.
How Tillarr checks Uptime Kuma
Without a key, Tillarr asks for /dashboard to see that Uptime Kuma is up. Every request goes from your device straight to your server, never through us.
Questions
Does Tillarr replace Uptime Kuma?
No. Kuma checks anything you point it at; Tillarr shows its results next to your services and passes its alerts on.
How do Uptime Kuma alerts reach my phone?
At 1.0, with Pro, add Tillarr as an ntfy notification in Kuma, and its alerts arrive like any other.