this post was submitted on 23 Sep 2023
11 points (100.0% liked)

Lemmy Support

4656 readers
15 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

I'm working on lemmy-meter which is a simple observability solution for Lemmy end-users like me, to be able to check the health of a few endpoints of their favourite instance in a visually pleasing way.

๐Ÿ‘‰ You can check out a screenshot of the pre-release landing page.


๐Ÿ’ก Currently, lemmy-meter sends 33 HTTP GET requests per minute to a given instance.

For a few reasons, I don't wish lemmy-meter to cause any unwanted extra load on Lemmy instances.
As such I'd like it be an opt-in solution, ie a given instance's admin(s) should decide whether they want their instance to be included in lemmy-meter's reports.

โ“ Now, assuming I've got a list of instances to begin w/, what's the best way to reach out to the admins wrt lemmy-meter?


PS: The idea occurred to me after a discussion RE momentary outages.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] bahmanm@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

Update 1

Thanks all for your feedback ๐Ÿ™ I think everybody made a valid point that the OOTB configuration of 33 requests/min was quite useless and we can do better than that.

I reconfigured timeouts and probes and tuned it down to 4 HTTP GET requests/minute out of the box - see the configuration for details.


๐ŸŒ A pre-release version is available at lemmy-meter.info.

For the moment, it only probes the test instances

  • enterprise.lemmy.ml
  • ds9.lemmy.ml
  • voyager.lemmy.ml

I'd very much appreciate your further thoughts and feedback.