32

I’ve got a lot of services, some in docker, some in LXC or a VM in proxmox. Currently I’ve got no monitoring service. Recently a service went down and I didn’t notice for quite a while so now I’ve got a bunch of missing data. What monitoring tools do you all use? Looking for something that works with docker and plain Linux CTs/VMs and can notify me if a website is down, docker container crashed, VM is offline, etc.

and as a bonus feature something that I can run on two machines so if an entire machine dies, the other will notice and I’ll still receive a notification.

notification can be anything, email, sms, push, etc.

you are viewing a single comment's thread
view the rest of the comments
[-] nitrolife@rekabu.ru 3 points 1 year ago

prometheus use own time series database. you can connect influxdb to grafana and send alarms from grafana, but alertmanager better i think. node-explorer can collect all this data (sensors, VM/PC load etc.)

[-] peregus@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

I've never used alerting in Grafana, how do they work? Is it possible to get alert if a ping is higher than xx for a period of time? What are alertmanager and node-explorer? Plugins or standalone tools? Sorry for all the questions! 😁 And thanks for the info!

[-] nitrolife@rekabu.ru 1 points 1 year ago

Grafana sends an email screenshot of the graph when an event is triggered on the graph. You can see alerts part on any graph for understand.

[-] peregus@lemmy.world 1 points 1 year ago

You know that I've never knew about that? I've just set it up! Thanks!!!

this post was submitted on 30 Jul 2023
32 points (86.4% liked)

Selfhosted

39700 readers
704 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 1 year ago
MODERATORS