You should not need a second tool to know that your site is down. dockxo’s Monitors page is an uptime checker in the same dashboard as the thing being checked, so a red monitor is one click away from the service’s logs.
Adding a monitor
Click Add monitor. Every domain in your account is offered in a searchable list, custom domains first, with load balancers and caches marked — or type any URL. Choose the interval (20 seconds to an hour), whether to follow redirects, the expected status code and an optional keyword that must appear in the body.
What you see
Up or down, response time, the last checks as bars, uptime for 24 hours, 7 and 30 days, a 24-hour latency chart and the list of incidents with their duration. The sidebar shows how many monitors are down right now.
What you get told
After the chosen number of failed checks in a row, the monitor goes down and an alert says why: DNS failure, connection refused, timeout, HTTP 5xx, TLS error. Another message comes when it is back, with how long it was down. Optional reminders while it stays down, a warning before the TLS certificate expires, Check now and pause.
Two kinds of channels
Alerts go to channels, and a monitor or a service can use several at once. Settings → Notifications holds them.
Telegram. Paste a bot token from @BotFather, send the bot a message from the chat or group you want alerts in, click Find chats and pick it. Send test confirms it works. The token is stored encrypted.
Email. Add an address and a name for it, up to 10 per account. Your own account address is ready at once. Any other address — the shared ops mailbox, a colleague, a client — gets a confirmation link first and receives nothing until it is opened. That keeps the panel from being used to spam anyone, and it means the person on the receiving end has agreed to be paged. The mail is short HTML with the same content as the Telegram message, sent from the panel’s own address.
Service notifications
Each service’s Settings tab has a Notifications card: which channels, and what to hear about — a failed deploy (and a successful one if you like), a container that stops without being stopped from the panel or keeps restarting, and when it runs again. Actions you take in the panel stay quiet. Managed databases add their own health alerts: down, replication stopped, lag over the limit, connections near the maximum.
A note on safety
Monitors never reach private addresses — localhost, private ranges, cloud metadata — including through DNS answers and redirects. The panel is shared by many accounts and a monitor must not become a way to probe someone else’s network. The same thinking is behind the email confirmation: an address only ever receives what its owner opted into.