[HELP] What's the best way to reach a given instance's admins - eviltoast

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.

  • bahmanmOPEnglish
    3•9 months ago

    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 🙏

    • @johntashEnglish
      2•9 months 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.

      • PenguinCoderEnglish
        1•9 months ago

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

        • @johntashEnglish
          3•9 months 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
            2•9 months 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•9 months ago

      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.

      • bahmanmOPEnglish
        0•9 months 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 🙂