this post was submitted on 12 Sep 2023
-1 points (0.0% liked)

Selfhosted

40782 readers
1613 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
 

I have enough machines on my network that I've long wanted to get better monitoring going on, and I finally bit the bullet and I'm trying to push through learning my way around grafana and prometheus/node extension. I have been following this guide: https://grafana.com/docs/grafana-cloud/monitor-infrastructure/metrics/metrics-prometheus/prometheus-config-examples/docker-compose-linux/ (great, btw!) but after importing the dashboards so I have three dashboards providing some intense readouts of three different machines, it got me wondering: how privacy protective is this? Is Prometheus just sending out a steady stream of diagnostic data for anyone to snoop on if they get access to my LAN? How can I/should I harden these setups to be privacy conscious?

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here