Uptime Monitoring Part 3: Tokyo Drift (Finale)

Okay. So. I'm gonna level with you. The previous "fix" helped but there were false positives sadly.

So I caved and a few days ago i got some stock notifications for servers and I got a new server in the family located in Bern, Switzerland with 1GB ram 1/4th of an 7950x3d (burstable) 25mbps networking (burstable to 10gbps)

Obligatory fastfetch of the VM

I got Uptime Kuma setup on there with PM2 & nginx and got it all loaded to monitor my servers.

And you would think this would work. aaaaaandd drum roll please. Did it work? NOPE.

As it turns out optime monitoring is a pain in the ass like anything on computers and is hard to make right.

Uptime Kuma keeps dropping requests from my discord bot that has a perfectly valid user agent of EvalynBot/UptimeMonitor/1.1 and nothing should be triggering it to drop. I had even implemented retries and yet it still fails

John ULTRAKILL

FAILURE AFTER FAILURE AFTER FAILURE
AFTER FAILURE AFTER FAILURE AFTER
FAILURE AFTER FAILURE AFTER FAILURE
AFTER FAILURE AFTER FAILURE

THE RESULTS REFUSE TO ALTER

AGAIN AND AGAIN AND AGAIN AND AGAIN AND
AGAIN AND AGAIN AND AGAIN AND AGAIN AND
AGAIN AND AGAIN AND AGAIN AND AGAIN AND
AGAIN AND AGAIN AND AGAIN AND AGAIN

MY FAITH BEGINS TO FALTER

So I give up I’ll just give it a bunch of retries and widen windows of things so it won't bother me or make the website say its down when it shouldn’t.

If it actually is down it's going to alert me anyway so it should be fine for a smaller scale personal deployment, and maybe it's just a bug with the software.

Maybe I should write my own? Maybe.

TLDR:
Uptime monitoring sucks and I got a proper dedicated VPS for it now.
Learn from my lessons and try to keep sane when doing this crap.