FreshRSS to keep track of as much as possible, along with Uptime Kuma and plain old bookmarks

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

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

I’m not, really. I run docker-compose and it runs. That’s it.

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.

I use portainer, not sure if that counts as a dashboard?

Users, monitoring your services for free since internet exists

dokploy.com

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.

If something goes down my kids will be a more immediate and annoying alerting tool than anything I’ve used professionally.

Arch packages. All services have systemd integration.

service still up = no problem
Can’t access service = problem, better ssh in

Simple as

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.

docker ps

Does dockge count as a dashboard?

‘Cause I use that to quickly check on what’s running, what’s stopped. Then I do most of my mainenance in a terminal, via SSH to the server.

I monitor everything with xymon, I get emails when there’s a problem. Works like a charm.

charity.wtf/…/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.)

docker stats

With that command, I get all the stats I need, no dashboards required.

github.com/nicolargo/glances

I do have Dashboards in Grafana, but I only use them to look something up. I have Prometheus Alertmanager connected to a Matrix bot that sends me messages when something looks wrong.

i am un-admining. free-range artisanal services wherever i happen to drop them. hell i don’t even know what’s running and what’s not until i try to access something.

i manage tech all day so my home tech is nothing but abject chaos and i’m ok with that. i have backups and i can go without if needed.

Bookmarks for linking to services. Grafana for graphs that I only look at if I am curious or looking into when a problem arises. I could use Uptime Kuma if I wanted a simpler solution or notifications.

I just simply dont monitor most things. I do have a few things such as low disk space and failed backups. They are just simple shell scripts that send me an ntfy message when there is a problem.

@kiol im using #pocketid to log in to my apps (if they are using #oidc), so I have everything there (in my apps section). If app doesn’t support oidc is there anyway, so instead of bookmarks I have everything there.

Unraid has a table of the docker containers.

I don’t need metrics or stats. I wouldn’t look at, or care about them anyway. Dashboards feel like tech enthusiast crap. Tech and resources for the sake of having tech. My services are to solve a problem, not look at metrics of.

Uptime Kuma monitoring anything I care about and notifying me via Matrix, or notifying me via email if it’s Matrix that’s down.

I just use Homepage as a bookmark/landing page so I remember what containers/services I have up and running so that I don’t need to check via terminal/portainer. Portainer/docker-compose files for managing services and that’s pretty much it. If I was using a dashboard I feel like I’d be wasting more time on an already time consuming hobby.

I mucked around with so many dashboards, homarr, homepage, dashy but settled on glance

Mainly because it’s minimalist and mostly text based. Handles my RSS feeds and anything that I want render I can usually vibe using the custom API widget.

github.com/glanceapp/glance

If Plex doesn’t add new shows/movies/music then I take a look at my services that should be adding stuff for Plex to serve up. That’s pretty much it these days.

I was using homepage but it seems to cause docker to die a LOT on my server.

Set of cron jobs that check services, then send a Matrix message if there’s an issue.

For the cron jobs, I pipe stderr to 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 call an api in technitium to register dns for all services when they are instantiated, and route everything through an nginx reverse proxy - Sonarr.internal.tld for example

I don’t use any kind of monitoring Or dashboards

Can you hear the fan? If no, it’s probably fine.

Never used a dashboard… I just manage my services on the cli with plain docker commands.

I use dashboards pretty often. Considering I’m in America, I use them just about any time I go anywhere, as nearly all automobiles have them.

i just ssh and run haproxymon on my reverse proxy running haproxy. It monitors all the end points availability, traffic…