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
[โ€“] Penguincoder@beehaw.org 2 points 1 year ago (8 children)

33 HTTP GET requests per minute to a given instance.

That is way beyond acceptable use, and would likely have your service blocked. There exists these services too :

https://lemmy-status.org/

https://lemmy.fediverse.observer/stats

Maybe those do what you're trying to do?

There is not an "admin inbox" for lemmy instances. You can hit the endpoint /api/v3/site for information about an instance including the admins list.

[โ€“] bahmanm@lemmy.ml 3 points 1 year ago (2 children)

beyond acceptable use

Since literally every aspect of lemmy-meter is configurable per instance, I'm not worried about that ๐Ÿ˜Ž The admins can tell me what's the frequency/number they're comfortable w/ and I can reconfigure the solution.

You can hit the endpoint /api/v3/site for information about an instance including the admins list.

Exactly what I was looking for. Thanks very much ๐Ÿ™

[โ€“] johntash@eviltoast.org 2 points 1 year ago (1 children)

Are these 33 different requests or do you hit the same endpoint multiple times?

I'd probably default to every 5 minutes at most, but I guess if it's up to the admin then it's all good. 33 requests per minute shouldn't be a ton of load if it's all read requests.

[โ€“] Penguincoder@beehaw.org 1 points 1 year ago (1 children)

Speaking as an admin of an instance here, 33 requests a minute is not "all good".

[โ€“] johntash@eviltoast.org 3 points 1 year ago (1 children)

Not without asking, but if the admin is okay with it then sure. I don't see the point of any sort of monitoring making that many requests per minute though.

[โ€“] activistPnk 2 points 1 year ago

Indeed. IIUC, OP said 33 reqs/min is a ceiling and tunable on a per-target basis.

If the target is a Cloudflare instance, you could perhaps even do 300 reqs/min without even being noticed.

[โ€“] Kangie@lemmy.srcfiles.zip 1 points 1 year ago (1 children)

I'm not worried about that ๐Ÿ˜Ž

You should be. Your name will be associated with abuse forevermore.

The admins can tell me what's the frequency/number they're comfortable w/ and I can reconfigure the solution.

Or you can set some sane defaults and a timeout period. 1 request / 5 mins is fine to check if something is online and responding.

[โ€“] bahmanm@lemmy.ml 0 points 1 year ago* (last edited 1 year ago)

sane defaults and a timeout period

I agree. This makes more sense.

Your name will be associated with abuse forevermore.

I was going to ignore your reply as a ๐ŸงŒ given it's an opt-in service for HTTP monitoring. But then you had a good point on the next line!

Let's use such important labels where they actually make sense ๐Ÿ™‚

load more comments (5 replies)