this post was submitted on 16 Jun 2023
11 points (92.3% liked)

Selfhosted

40183 readers
1032 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 1 year ago
MODERATORS
 

running a lemmy instance has learned me a lot about devops already!

I love playing around with this, the lemmy instance was a great reason. lemmyfly.org doesn't have a lot of traffic yet, I think it can handle some more. Currently running on 2 vcpu/4gb ram.

After chatting to my devops colleague at work I wanted to set up a Grafana dashboard with metrics on the server. Seems it's pretty pretty doable!

  • I installed prometheus node_exporter on my lemmy server
  • I created a second server at my VPS. Very cheap, and don't think I'll be running the Prometheus/Grafana 24/7 so I'll just create a snapshot of it, destroy the server and re-create when wanted
  • Created an internal private network so the instances can communicate without exposing ports to the public
  • Installed Prometheus on the new prometheus server
  • Installed Grafana
  • log in to Grafana, admin:admin then change password
  • Go to the Grafana home dashboard, click on + sign and click on Import. In Import via grafana.com, put the dashboard id 1860 (preset for all prometheus node_exporter metrics) and click on Load.
  • Done!

Last 2 hours in the garden with a beer on the side, WFH FTW

top 5 comments
sorted by: hot top controversial new old
[–] Wesleysnoops@reddthat.com 1 points 1 year ago (1 children)

Very cool! What's bandwidth and system consumption been like so far?

[–] majorswitcher@lemmyfly.org 1 points 1 year ago

actually I did delete the server (after creating a snapshot of it) a week or so ago. But this morning I wanted to check lemmyfly.org, couldn't load the page. Checking my Hetzner dashboard I noticed CPU was spiked at 200%?! It did drop again though, but apparently had last for 2-3 minutes. But prometheus was down, so no graphs apart from the hetzner ones. I doesn't relate to network traffic spikes, so I don't know what caused it. I've started the prometheus server again (that snapshot was really useful :) ) and will leave it on for a couple of months now.

current system consumption:

I might need to get an extra volume for storage, Lemmy is starting to eat up the root filesystem.. Does anyone know how I re-configure Lemmy to look at a different volume for storage ?

[–] manned_meatball@lemmy.ml 0 points 1 year ago* (last edited 1 year ago) (1 children)

lol I literally did this yesterday for my job, using dashboard 1860 too. I used a docker compose stack following their guide here.

[–] majorswitcher@lemmyfly.org 0 points 1 year ago (1 children)

i'm now looking into logging more specific http request data. Maybe https://github.com/martin-helmich/prometheus-nginxlog-exporter?

[–] majorswitcher@lemmyfly.org 1 points 1 year ago

http_response metrics are also up, using https://github.com/martin-helmich/prometheus-nginxlog-exporter

would be nice to see the numbers go up :)