Live data from Hacker News

Monitoring My Homelab, Simply

b.tuxes.uk

1–10 of 70 posts

Re: Monitoring My Homelab, Simply

#3
I understand your pain.

I used to have sensu, but it was a pain to keep updated (and didn't work that well on old rpis)

But what I did find was a good alternative was telegraph->some sort of time series (I still really like graphite, influxQL is utter horse shit, and prometheus's fucking pull models is bollocks)

Then I could create alert conditions on grafana. At least that was simple.

However the alerting on grafana moved from being "move the handle adjust a threshold, get a a configurable alert" to craft a query, get loads of unfilterable metadata as an alert.

its still good enough.

Re: Monitoring My Homelab, Simply

#6
post #4

Even in homelab you should totally monitor thing like - raid health - free disk space - whether backup jobs running - ssl certs expiring

One could also look every Sunday at 5 pm manually through this stuff. In a homelab, this can be enough.

One cold also just wait for things to not work before to try and fix them

Re: Monitoring My Homelab, Simply

#7
post #4

Even in homelab you should totally monitor thing like - raid health - free disk space - whether backup jobs running - ssl certs expiring

One could also look every Sunday at 5 pm manually through this stuff. In a homelab, this can be enough.

Look I agree but one can also manage with an always on pc and an external hard drive instead of a homelab. It's part hobby part learning experience.

Also if you have kids 0-6 you can't schedule anything relaibly

Re: Monitoring My Homelab, Simply

#9
post #6
post #4

Earlier quoted context omitted.

One could also look every Sunday at 5 pm manually through this stuff. In a homelab, this can be enough.

One cold also just wait for things to not work before to try and fix them

For backups that's usually not the best strategy.

Re: Monitoring My Homelab, Simply

#10
I use Prometheus + Prometheus Alertmanager + Any Free Tier paging system (currently OpsGenie, might move to AlertOps).

Having a feature-rich TSDB backing alerting minimizes time adding alerts, and the UX of being able to write a potential alert expression and seeing when in the past it would fire is amazing.

Just two processes to run, either bare or containerized, and you can throw in a Grafana instance if you want better graphs.

Post reply on HN