16

I am using hd-idle (see link) to spin down my one external hard drive on my RPI server. It is not used for large parts of the day and night so it has been quite useful to set up hd-idle, which spins down the drive after an hour or so of no activity.

Now hd-idle can generate a log file where it notes down some data, e.g. when the drive was spun down, how long it was running, what time it spun down.

You can read the file to get an impression how well it works, but I'd like to see the data visualised or analysed in some way. Seeing the past month of how often per day the drive was spun down, or average length of long it was running and so on.

Searching online I couldn't really find anything. Maybe anybody here knows more? Or what ways of recording and looking at this type of data are you using?

you are viewing a single comment's thread
view the rest of the comments
[-] markstos@lemmy.world 0 points 4 months ago

I recommend generating some metrics from the logs and graphing them yourself.

Perhaps the free Grafana plan would have what you need to parse the log files and visualize the metrics you want.

[-] RootBeerGuy@discuss.tchncs.de 2 points 4 months ago

I get your point and it was an emergency option to at some point take time and do it myself, sure. But that is not what I asked, not even sure when I have the time to do this.

[-] markstos@lemmy.world 1 points 4 months ago

There aren’t log visualizers for every artisanal log file format. But there’s a movement towards supporting JSON format logs for more services, and lots tools that can understand JSON logs making generating graphs and metrics from arbitrary logs fairly efficient.

If this tool is making the logs harder to parse by using a custom format, that’s something the tool could improve.

Some apps support both plaintext logs for humans and JSON logs for tools.

this post was submitted on 27 Aug 2024
16 points (100.0% liked)

Selfhosted

40716 readers
433 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS