this post was submitted on 12 Oct 2026
41 points (93.6% liked)

Selfhosted

62908 readers
1013 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Have been working on my Grafana dashboard recently and am thinking about what else I could add. So far, I have:

  • CPU usage and temperature
  • Memory usage
  • Network usage
  • Backrest daily backup status
  • SMART status of drives
  • CPU and memory usage of containers

Anything else that you find useful? I have a few other ideas, but am curious what others have up. Is everything on one scrollable dashboard, or do you have it organized across multiple?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] ultimaluz@lemmy.world 2 points 5 hours ago (1 children)

I'd add backup age and size, not just status, like alert if the newest dump is older than ~26h or smaller than 1MB, a job can say success and still leave you a useless file. and disk fill with a threshold, not only the graph. learned that one the hard way, a table on my vps was getting a row every minute with no cleanup and one day the disk hit 100% and postgres just died for like 40 min, obviously nobody was looking at the dashboard right then lol. now 80% warns and 90% sends me an email, and uptime kuma checks the cert expiry from outside. I guess the dashboard is nice to look at but the stuff that matters should ping you

[โ€“] glorp@lemmy.world 1 points 19 minutes ago

Size is a great idea, thanks. The problem with backup age is that Backrest doesn't expose a metric for when the backup was attempted, so right now it's just checking for failure status daily. That, of course, fails if backrest doesn't attempt a backup for whatever reason. Chances of that happening, I don't know, but I'll have to look into implementing the metric (or label, I suppose) myself.