- Check any URL every 20 seconds to an hour, follow redirects, check status and an optional keyword
- Up/down, response time, last checks as bars, uptime for 24 h / 7 d / 30 d, 24-hour latency chart, incidents
- Alert with the reason (DNS, refused, timeout, HTTP 5xx, TLS…) and one when it is back
- Two channel types: Telegram chats and email addresses, up to 10 addresses per account
- Reminders while down, TLS certificate expiry warning, Check now and pause
- Service notifications: failed deploy, container that stops or keeps restarting, and when it runs again
Monitors
The Monitors page works like Uptime Kuma, built in. Add a monitor for any site — your own domains are offered in a searchable list, custom domains first, with load balancers and caches marked — and the panel checks it every 20 seconds to an hour, follows redirects, checks the status code and optionally a keyword. Each monitor shows up/down, response time, the last checks as bars, uptime for 24 hours, 7 and 30 days, a 24-hour latency chart and its incidents. The sidebar shows how many are down.
After the chosen number of failed checks in a row the monitor goes down and an alert says why: DNS, connection refused, timeout, HTTP 5xx, TLS. Another one comes when it is back, with how long it was down. Optional reminders while it stays down, a warning before the TLS certificate expires, and Check now / pause.
Monitors never reach private addresses (localhost, private ranges, cloud metadata), including through DNS answers and redirects, since the panel is shared by many accounts.
Channels: Telegram and email
Settings → Notifications holds the channels alerts go to. A monitor or a service can send to any number of them, so the on-call chat and the ops mailbox get the same message.
Telegram. Paste a bot token from @BotFather, send the bot a message, and Find chats lists the chats to choose from; Send test checks it. The token is stored encrypted.
Email. Add up to 10 addresses per account. Your own account address needs no confirmation. Any other address gets a confirmation link first and receives nothing until its owner opens it, so nobody can be signed up for alerts they did not ask for. Alerts arrive as short HTML mails with the same content as the Telegram message.
Service notifications
A Notifications card on each service’s Settings tab chooses the channels and what to hear about: a failed deploy (a successful one if you like), a container that stops without being stopped from the panel or keeps restarting, and when it runs again. Stops, restarts and deploys started in the panel stay quiet. The card also lists the service’s domains with their uptime monitor, or a button to add one.
Database health
Managed MariaDB services are checked every minute: whether the database answers, whether a replica’s replication threads run, how far behind it is, and whether connections pass 90 % of the maximum. Each problem is announced once when it starts and once when it is over, on the channels you picked.