Selfhosted

40338 readers

840 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

What's Your Preferred Server Monitoring Method? (self.selfhosted)

submitted 9 months ago by Trincapinones to c/selfhosted

68 comments fedilink hide all child comments

How do you monitor your server containers, disks, load...?

Do you use an easy-to-use web interface? Do you do everything via SSH? Or maybe you've got a more complicated setup?

I want to change my setup and I'm looking for new ideas, I've been using Cockpit for some years and some of the plugins are really outdated (ZFS for example) and others are completely broken (docker-compose).

you are viewing a single comment's thread
view the rest of the comments

[–] sysadmin420 5 points 9 months ago* (last edited 9 months ago) (1 children)

I've been using uptime Kuma recently and it's great but works better outside of docker.

Inside docker I'd get a lot of false down positives from I assume docker throttling the checks.

Plus it works with email, telegram, and matrix chat alerts. I monitor all my clients sites with it, and it's bullet proof behind caddy.

[–] thirdBreakfast 1 points 9 months ago (1 children)

For light touch monitoring this is my approach too. I have one instance in my network, and another on fly.io for the VPSs (my most common outage is my home internet). To make it a tiny bit stronger, I wrote a Go endpoint that exposes the disk and memory usage of a server including with mem_okay and disk_okay keywords, and I have Kuma checking those.

I even have the two Kuma instances checking each other by making a status page and adding checks for each other's 'degraded' state. I have ntfy set up on both so I get the Kuma change notifications on my iPhone. I love ntfy so much I donate to it.

For my VPSs, this is probably not enough, so I am considering the more complicated solutions (I've started wanting to know things like an influx of fali2ban bans etc.)

[–] sysadmin420 2 points 9 months ago

I just do web hosting for clients sites and use Kuma to monitor uptime and SSL certificates.

Ive got multiple Kuma's running as well.