HTTP and keyword
I check the page, the status code, redirects and whether the page still contains the expected text — not just “200 OK”.
Infrastructure 06.7 — Monitoring
Uptime Kuma — monitoring for servers and services
Before a client calls you about a problem, the system should already know. I deploy and run Uptime Kuma — websites, services, ports and certificates on one dashboard, with alerts to Telegram or email.
- 60s
- Check interval
- 90+channels
- Notification routes
- 0GEL
- Licence cost
Uptime Kuma / capabilities
What it covers
HTTP, TCP, ping and DNS monitoring, history, a public status page and alerts — on your own server, with no subscription.
TCP ports and ping
SMTP, SSH, RDP, a database or just a host — I check whether the port is open and the machine answers.
Certificate expiry
A warning arrives days before an HTTPS certificate expires — the site never “suddenly” stops opening.
Notifications
Telegram, Slack, Discord, email, SMS or a webhook — over 90 channels, with escalation rules.
Status page
A public or password-protected page where the client sees what works and what does not — without calling.
History and SLA
Response-time charts, uptime percentage and incident history — ready data for a monthly report.
process
How the process runs
-
01
Inventory
Which service is critical, what must be available 24/7 and who should receive the alert.
-
02
Deploy
Uptime Kuma as a Docker container, with its database and a backup — running in 10 minutes.
-
03
Alerts
Connecting channels, escalation and a test incident — so you know the alert really arrives.
-
04
Operate
Updates, adding new monitors and a monthly availability report.
cases
Examples
The site went down at night
A Telegram alert within 40 seconds — the problem was found before anyone had to call.
An expiring HTTPS certificate
A warning 14 days ahead — renewed in time, with no browser warnings.
faq
Common questions
Does it cost anything?
No. Uptime Kuma is open source and free — the only cost is the server it runs on.
Where does it run?
As a Docker container on your server or a Proxmox VM. Monitoring must be independent of the system it watches.
Where do the alerts go?
Telegram and email by default; Slack, Discord, SMS or a webhook into your own system when needed.
All directions
Other sub-directions
Want to be the first to know?
I will prepare the monitoring list and deploy Uptime Kuma — in one evening.
Let’s talkContact
Get in touch about your technical task
Contact me by phone or WhatsApp. Critical incidents are covered 24/7; other requests are handled within the agreed support schedule.
24/7 on critical incidents — Response mode
If I miss your call, I will get back to you.