this post was submitted on 04 Dec 2024
20 points (95.5% liked)

Selfhosted

40696 readers
300 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I'm looking for a simple remote system monitoring and alerting tool. Nothing fancy. Do you know of any? Features:

  • monitors CPU, memory and disk space
  • can accept multiple hosts to watch
  • has some sort of alerting system
  • can be deployed as a single docker container
  • can be configured using a text file
  • configs can be imported and exported inside the docker compose file

I like uptime-kuma but it only records the uptime. Other containers I've found seemed to be overly complicated. They requires multiple docker containers for log aggregation etc...

you are viewing a single comment's thread
view the rest of the comments
[–] Mora@pawb.social 4 points 2 weeks ago (1 children)
  • monitors CPU, memory and disk space
  • can accept multiple hosts to watch
  • has some sort of alerting system
  • can be deployed as a single docker container
  • ~~can be configured using a text file~~
  • ~~configs can be imported and exported inside the docker compose file~~

https://github.com/henrygd/beszel

There is no really config to speak of. You setup the hub. Then you click on add system and write in the IP. Then you click on "Copy compose". That is the agent you can then deploy with a compose file on any system. Click on add and it is there.

The only thing you might want to configure is alerting, but only once on the hub.

[–] Agility0971@lemmy.world 1 points 2 weeks ago (1 children)

ahh so the remote system needs to have the docker stack as well then. hmm, that might be an issue :p

[–] Mora@pawb.social 1 points 2 weeks ago

There is also a CLI without docker, for agent and hub, and you can mix & match. I can't say how well though, very happy with running it as docker compose.