I’m currently using InfluxDB + Telegraf + Grafana combination to monitor Linux systems and k3s pods. It’s basically same as Prometheus, but InfluxDB uses push model, which makes it easier to develop tools for collecting custom time series data.
For alerts and dashboards, I think Grafana is the simplest and most hassle free solution available at the moment.
I have a APC Back-UPS 1600VA. It powers two desktop PC/Server, a monitor, and router. So far, it gets the job done.
The biggest downside is; battery is not user replaceable, at least it’s not straight forward like the other models. If possible, prefer a UPS with the easy battery replacement option.
Biggest difference is being able to execute INSTCMD commands, at least that was the main reason why I developed my own tool. Another less important differences are: older ARM support and since it’s written in Rust, it’s much more efficient in terms of resource usage. TBH, being that efficient only makes sense for very low-power devices.
Besides that, I don’t think you can go wrong with either project.
Thanks! I appreciate any kind of feedback.
I’m actively using ollama with docker to run llama2:13b model. It’s generally works fine but heavy on resources as expected.
I personally use Traggo, but TimeTagger is also a great option: https://timetagger.app/articles/selfhost/
If I’m recall correct, Sugo 13 only has single 3.5 slot. I’d say look for Sugo 14 (2x3.5) or Node 304 (6x3.5)
Make sure all of your components fits to the planned case including power supply.
Instead of single pool, I simply split my drives into tiers: cache, storage, and trash due to limited drive counts. Most R/W goes to the cheap trash and cache disks instead of relatively new and expensive NAS drives.