A monitoring panel inside Telegram
Servers, services and incidents at a glance — from a button in the chat, with no browser and no dashboard login.
Running in production since 31 August 2026
See the screens
Case studies
Five write-ups: what happened, what I measured, what I did and how I verified it. One is a product of my own with screenshots, another is a write-up of my own mistake.
The disk was filling up. It was the logs
System journals had grown to 4 GB and kept going. Free space was shrinking and the applications had nothing to do with it.
4.0 GB → 31 MB, growth stopped, no restarts
Read the write-up
Monitoring from scratch without touching production
There were no metrics at all; service health was judged by whether the site opened.
A separate observation server; production exposed no new ports
Read the write-up
One failure, one notification
Two independent watchers reported the same thing, and some messages carried no cause at all.
Seven duplicates removed after coverage was proven
Read the write-up
Monitoring that lied
The observation host lost network connectivity and declared five healthy sites down.
False alarms of this class stopped
Read the write-up
And what remains afterwards
Example report
In every case the result is not only a fixed system but also a document you can re-read six months later.