Cross-posted from https://lemmy.ml/post/5719058
I’ve been working on a simple opt-in solution, primarily for Lemmy end users like me (but also helpful for admins), to easily check the status/health of their favourite instance.
You can find the details of the implementation in 
lemmy-meter github repo.
❓ @admins: would you be interested in adding your instance to lemmy-meter?
You don’t need to do anything except confirming - I’ll handle the rest. It should only take a few minutes for your instance to show up in lemmy-meter.
Out of the box it will send only 4 HTTP GET requests per minute to your instance. However that is totally configurable if it sounds too much or too little.
Removed by mod
The larger Lemmy world terrifies me. It’s like a technological eldritch horror that I have somehow survived entering it’s domain.
sure, go for it. That said, 4/minute seems a little high, mostly just because usual guidance is that a heartbeat check should be done about once a minute for web services, but 4 is also not unserviceable.
To be precise, it’s not 4 requests to the same endpoint.
lemmy-meter probes 4 endpoints each once per minute:
- The landing page
api.getPosts(limit=1)api.getComments(limit=1)api.getCommunities(limit=1)
That’s b/c I’ve frequently experienced cases when the landing page works but some mobile APIs don’t and vice versa.
Hope that makes sense.
As I said, if after some time you feel like this is too much load, reach out to me and I can easily configure lemmy-meter to probe less frequently.
Oh, ok, if its four different calls for different end points then that makes sense.
Update 1
ttrpg.network is now on lemmy-meter 🥳 Thanks for your interest 🙏
