Skip to content
Register

Monitoring 20 VPS for $2.00/month

General Discussion by adam20 6 replies 554 views
adam20

Member OP

Ex-Abuse Desk

2 #1

The ticket said "your server is sending SYN floods" so I checked. It was my own monitoring script pinging every 30s from a $3/mo box that cost more than the things it watched.

Stack:
- Uptime Kuma on a Hostinger $24/yr KVM
- Telegram bot for alerts
- healthchecks.io as dead-man switch

Total: $2/month if you count the Hostinger box as monitoring-only. The ticket said I should write a guide so here we are.

Uptime Kuma does HTTP/tcp/ping. Telegram is free. Healthchecks.io free tier covers 20 checks. The ticket said nothing about rate limits but I've hit none.

reported. resolved. repeat.
YuriDavid

Member

#2

---
- NOTE: Hostinger $15/yr is actually $1.25/mo
- WARNING: this makes monitoring 40% of server cost
- alternative: run Kuma on your "biggest" VPS
- but then: monitoring dies with server
- ---
- fallback architecture:
- primary: Uptime Kuma on Node A
- secondary: healthchecks.io (external)
- tertiary: second Kuma instance on Node B watching Node A
- ---
- cost breakdown:
- Telegram: $0
- healthchecks.io: $0
- Hostinger: $2.00/mo
- true monitoring cost: $0.10 per VPS

indentation is not optional
svendeal

Member

Deal Sniper

#3

Found Hostinger $24/YR ARE YOU KIDDING on black friday 2023, price history says they never repeated it my Kuma has been up 847 days on that box.

Uptime Kuma + Telegram = instant alerts when my $9/YR RackNerd dedis die (often) (RIP 2024)

🏃 adding healthchecks.io now, didnt know free tier did 20

world record: 4min Arch install
ZH

Member

#4

The Node.js install is identical. I monitor 8 Windows VPS and 4 Linux ones from a single Hostinger instance.

No performance difference in my experience. The Telegram webhook doesnt care about OS.

LichunLars

Member

#5
adam20 said:
My own monitoring script pinging every 30s
old script:  30s interval, 20 targets, 57600 pings/day
route via HE to target #1: 12ms
route via cogent to target #7: 34ms (packet loss 2%)

Kuma default: 60s interval, 20 targets, 28800 checks/day
route via any: ~same latency, cleaner headers

Route via cogent adds 22ms on your worst target. Kuma's HTTP check is lighter than ICMP flood. Route via HE is stable enough for alerting.

1ms or I don't want it
annexbi

Member

6 #6

(I tried to write this as a wiki contribution) (the form said "keep it concise") (which is funny because) (have you met me) the changelog for next release (I checked the repo) (yes I am that person) credits adam20 (not me) (correctly) for the fallback section (which I may have expanded slightly) (the nested parenthetical section) (they kept it) (drives people mad) (but it works)

push. done. coffee.
KI

Member

#7

Hostinger still sells that $2/mo plan?

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft