Selfhosted

60409 readers

464 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Simple remote system monitoring tool (lemmy.world)

submitted 2 years ago* (last edited 2 years ago) by Agility0971@lemmy.world to c/selfhosted@lemmy.world

23 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

[–] TCB13@lemmy.world 1 points 2 years 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@lemmy.world 1 points 2 years ago (1 children)

https://guide.munin-monitoring.org/en/latest/tutorial/getting-started.html#adding-a-node

[–] TCB13@lemmy.world 1 points 2 years 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.

[–] waldek@lemmy.86thumbs.net 1 points 2 years 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.