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

Selfhosted

40651 readers
350 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
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
20
Simple remote system monitoring tool (self.selfhosted)
submitted 2 weeks ago* (last edited 2 weeks ago) by Agility0971 to c/selfhosted
24 comments fedilink hide all child comments
 

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
[–] [email protected] 8 points 2 weeks ago (5 children)

Munin might be what you're looking for. Very simple and easy to write your own plugins for if some information is missing.

http://munin-monitoring.org/

[–] TCB13 1 points 2 weeks ago (2 children)

Looks cool, what about security? Since you’re experienced with it, how does it access the information of the nodes and how secure or insecure that may be? At the end of the day I don’t want to open a port on all nodes just to have it be used as root access to those machines…

[–] anamethatisnt 1 points 2 weeks ago (1 children)
[–] TCB13 1 points 2 weeks ago

Yeah, I was typing that on the phone... thanks for the link:

As the node runs as the root user in order to run plugins as any needed user, it now only listens on localhost as a security measure. You have to edit munin-node.conf in order to listen to the network, and add the master’s IP on the authorized list.

So, I guess the best approach is to just run it inside a management network / internal VPN to avoid exposing the port to the internet.

[–] [email protected] 1 points 2 weeks ago

You could add encryption and authentication via ssh: https://guide.munin-monitoring.org/en/latest/example/transport/ssh.html or you could put it behind an nginx and wrap it in tls if you just want encryption.

load more comments (2 replies)