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.

  • johntash@eviltoast.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    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.

      • johntash@eviltoast.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        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@slrpnk.net
          link
          fedilink
          arrow-up
          2
          ·
          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.