1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
---
layout: post
title: Monitoring with Uptime Kuma
date: 2025-03-06 18:55 +0100
lang: en
---
[Recently](https://furry.engineer/@uvok/114026509150081909), I wanted to do add
some kind of monitoring to my servers. The prevalent reason was monitoring my
AS, which I accidentally broke by shutting down one server, or the hosting
provider had an outage (This was because I didn't configure a fallback default
route, but that's another story).
So, I took a look at the monitoring landscape. And immediately wanted to drop
the idea again, because there were too many choices. And had no intention to
install and test them all, and no energy to read dozens of websites with user
reports.
But then I said, "wait. Let's not do it the overthinking way again". So I took
the first best/simple thing and chose [Uptime
Kuma](https://github.com/louislam/uptime-kuma). I actually wanted to drop it
right away once I saw it's running on NodeJS (ehhh). But then I decided to spin
up an LXC on my Proxmox anyway.
And lo and behold, it works:
{% image
img="https://pics.uvokchee.de/_data/i/upload/2025/03/06/20250306175521-4763fdf7-me.png"
alt="Screenshot of Uptime Kuma - showing the ping times of various servers."
%}
And it even has a certificate validity check.
{% image
img="https://pics.uvokchee.de/_data/i/upload/2025/03/06/20250306175521-7805c0bb-me.png"
alt="Screenshot of Uptime Kuma - showing the HTTPS monitor, including the
remaining certificate validity time."
%}
It runs in my home network, so I can actually detect whether my AS is reachable
(to a degree). And it brings various notification options, from which I chose
Telegram and Matrix.
I actually got an outage notification this week, on my Hetzner servers. No idea
what happened there, though, I didn't receive an outage report / notification
from them.
|
