Selfhosted

60409 readers

491 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

[–] Mora@pawb.social 4 points 2 years 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 years ago (2 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 years 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.

[–] dan@upvote.au 1 points 1 year ago

You don't need Docker. The agent is a single executable file so you could just manually copy it to /usr/local/bin if you wanted to.