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.
Interesting, FYI there is a similar project: https://lestat.org/
Thanks for the link. Had no idea about that.
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.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.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 🙏
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
I’d very much appreciate your further thoughts and feedback.
Why does it need to make 33 requests per minute? Surely the data doesn’t have to be that up to date?
Agreed. It was a mix of too ambitious standards for up-to-date data and poor configuration on my side.
