Running services, network usage, memory usage, bandwidth, disk I/O, successful logins, whether the thing is even alive, etc…
So far my only method has been “hope and pray”.
I have a robust monitoring system for my Jellyfin server, been running for the last few years. Checks in periodically, at least once per 24 hours and notifies me if it’s down. Doesn’t use any electricity, but does consume a good amount of Cheerios and mac & cheese.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters AP WiFi Access Point DNS Domain Name Service/System ISP Internet Service Provider LXC Linux Containers NAS Network-Attached Storage NFS Network File System, a Unix-based file-sharing protocol known for performance and efficiency RAID Redundant Array of Independent Disks for mass storage SSH Secure Shell for remote terminal access TLS Transport Layer Security, supersedes SSL ZFS Solaris/Linux filesystem focusing on data integrity
10 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.
[Thread #122 for this comm, first seen 9th Oct 2026, 13:00] [FAQ] [Full list] [Contact] [Source code]
I have the best detector for issues with my self hosted services: my wife!
Thats cool! My wife thinks i’m crazy just because i homeserve …
Uptime Kuma, only really care if it’s up or not. Got about 30 services monitored, sending notifications to Signal.
Ah cool! How do you get notifications sent to signal. I’ve always avoided because i didnt like emails of my home setup leaving home in clear
https://github.com/bbernhard/signal-cli-rest-api
Its very finicky to setup, but once you get it working its pretty good. Sometimes needs to be reauthenticated though.
Kuma notification settings:
Looks like i don’t have to expose ports or anything like that, right?
Nope, your uptime kuma speaks to it directly, and it basically acts as a signal client for you.
Edit: ah, i see! It’s kuma that allows you to i guess by adding new device on phone Signal
I started with uptime kuma since it was simple and light on resources. I’ve switched to checkmk community (formerly raw) and really enjoying it. It’s telling me so many things that are wrong that I missed. Like that one time I made a snapshot of a VM then forgot about it for 113 days…
@Limeade3425 @user224 how did you discover that with checkmk?
With Uptime Kuma, I just used ping and http sensors so that I knew my stuff was up. When I switched to CheckMK, I installed the agent on all servers and that brought quite a bit more info in, then I added the Proxmox integration and that gave me the snapshot info (as well as more info). I think it automatically pulled in my ZFS info, like zpool status. Then added smart monitoring to my storage so that I can see that my hard drives have been spinning for 13 years and 266 days 😅
13 years?? That machine has never gone fown fo 13 years??
Sorry 😂 I was referring to Power-on hours, so total hours it’s been on (not necessarily consistently)
