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.
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/sitefor information about an instance including the admins list.Each server would have its own acceptable use policy. Also consider the social detriment of Cloudflare nodes. We could even say @bahmanm@lemmy.ml has a moral /duty/ to overwork the Cloudflare nodes :)
@Blaze@discuss.tchncs.de: thanks for pointing out lestat. Thatβs one of the very few services of this kind to be responsible enough to red-flag the Cloudflare nodes. I hope @bahmanm@lemmy.ml follows that example; though it could still be improved on.
Itβs misleading for any tor-blocking Cloudflare node to have a 100% availability stat just because by design it deliberately breaks availability to a number of users in an arbitrarily discriminatory fashion. https://lemmy-status.org/ and https://lemmy.fediverse.observer/stats do a bit of a disservice by not omitting or flagging #Cloudflare nodes.
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.
Exactly what I was looking for. Thanks very much π
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.
Speaking as an admin of an instance here, 33 requests a minute is not "all good".
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.
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.
You should be. Your name will be associated with abuse forevermore.
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.
I agree. This makes more sense.
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 π