I know dashboards are super trendy, but I’d love to hear from those who are not using them. I personally use FreshRSS to keep track of as much as possible, along with Uptime Kuma and plain old bookmarks. Perhaps there is a better overview solution, but I also love filtering what I see to not feel overwhelmed. or spammed, by information.
service still up = no problem
Can’t access service = problem, better ssh inSimple as
If something goes down my kids will be a more immediate and annoying alerting tool than anything I’ve used professionally.
I have just reduced the number of services to the couple I actually use, which I mostly remember exist. I have my own domain, so each service is service.mydomain.tld
Same for me. I use most of my services multiple times a week, so I find out pretty quickly if one isn’t working.
Same here 🙂 Last 3 times, things have broken because zfs raid on usb-connected DAS is not a great idea 😅😅
Even though Level1Tech said it works 😶🫣 https://youtu.be/GmQdlLCw-5k from 11:11 . Maybe terramaster use bad usb chipset.
I used a hodge-podge of chinesium parts and leftover drives to create a DAS system that hooks up to an HBA via DAC. I’m actually kinda surprised how stable it’s all been.
If I had time to make dashboards, I wouldn’t waste it making dashboards. Most of the stuff I have just works without a lot of attention, and that’s the way I like it.
I just wait for someone to scream if it breaks.
Never used a dashboard… I just manage my services on the cli with plain docker commands.
Can you hear the fan? If no, it’s probably fine.
Oh man, I thought it was “just” me 🤣 To be fair, the light counts as well (Qnap).
I don’t know how you guys function without some sort of visual. I will forget everything I’m running if it’s not on a dashboard of some sort. That’s not a maybe - it’s guaranteed. Because it’s happened before.
Kubernetes with
- helm
- the Kubernetes version of compose files
- fluxcd
- manages the helm releases
- renovate
- scans my github kubernetes repo for dependencies and creates pull requests for updates
- helm
I use portainer, not sure if that counts as a dashboard?
Arch packages. All services have systemd integration.
Set of cron jobs that check services, then send a Matrix message if there’s an issue.
For the cron jobs, I pipe
stderrto another script that watches those and does the same.If all fails, and internet is unavailable and the router crashes, a Pi will toggle a relay, cutting and resupplying power.
I tried portainer for a while, but it was almost useless to me, as I’d always end up in the command line anyway. So I dropped that and any other dashboard idea.
FreshRSS to keep track of as much as possible, along with Uptime Kuma and plain old bookmarks
I monitor everything with xymon, I get emails when there’s a problem. Works like a charm.
https://charity.wtf/2021/08/09/notes-on-the-perfidy-of-dashboards/
Graphs and stuff might be useful for doing capacity planning or observing some trends, but most likely you don’t need either.
If you want to know when something is down (and you might not need to know), set up alerts. (And do it well, you should only receive “actionable” alerts. And after setting alerts, you should work on reducing how many actionable things you have to do.)
(I did set up Nagios to send graphs to Clickhouse, plotted by Grafana. But mostly because I wanted to learn a few things and… I was curious about network latencies and wanted to plan storage a bit long term. But I could live perfectly without those.)
