this post was submitted on 12 Sep 2023
15 points (89.5% liked)

Selfhosted

60210 readers
999 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.

Resources:

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

Questions? DM the mods!

founded 3 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?

top 1 comments
sorted by: hot top controversial new old
[–] peter@feddit.uk 6 points 2 years ago

Since you don't need access to prometheus you could limit it to be only accessible by grafana and the servers you are pulling from. Other than that, you should read this https://prometheus.io/docs/operating/security/