Let me introduce my new little project - 🍋 LemMon - Lemmy Monitor - Servers Status
The main servers will check if the lemmy servers (you can request in this post which servers to add) are online every 1 minute.
Every lemmy server have dedicated status page like lemmy.world: https://lemmon.zerobytes.monster/index?server===wM
Enjoy!
I’d also suggest going through and adding these, or even integrating it into this
lemmy.ca is pretty big now which is nice to see
What exactly does this check? a ping? trying to retrieve something from the API?
Not all servers
Your client may have a bug, you commented 13 times
yes sir just delete all , lemmy.pt server went crazy in the time im posting and bean for ios to
@null On one hand I strongly prefer kbin to lemmy, but on the other hand that is a clever name for the tool! I like it!
why not uptime-kuma?
Because i dont like uptime-kuma and i know how to write a code 😜
Best answer. Really like your UI design! (I like uptime-kuma tho)
This looks like a fork of it.
You are totally wrong here
Please add waste-of.space. Thnx!
Please add cocte.au and leminal.space
Any plans for monitoring kbin instances?
Yes ;)
Please add lemmy.fmhy.ml to that list - it’s been down for over a day due to the .ml issues but have been looking for something like this to see if its back.
I don’t think .ml is coming back. They won’t be able to renew the domain because of issue with the registrar in Mali
Wont add sorry, the domain is lost.
it wont be coming back on the same domain
Great tool! Any chance of feddit.uk?
Removed by mod
Can you add programming.dev?
Added 😀
I like it! Can you add my instance? lemmy.g97.top
This is awesome! I’d love to have my own added, despite it still being tiny.
Every one minute seems… excessive. I know this is social media but still, what would be bad about reducing that to like once per hour, to reduce the load across the entire Fediverse?
I think you’re underestimating the number of requests that a server can handle. Even my tiny instance currently sees dozens of requests every second and is very lightly loaded. A single request per minute is an immeasurably small load.
A single health check call a minute by a single app is nothing compared to real world usage
True, but if we agree that every second is too frequent, but that every day is too sparse (maybe?), then the question becomes one of optimizing the choice of what frequency would be best for whatever outcome.
Like if it was every 5 minutes, that would cut down on the amount of traffic 5-fold, and still give 12 checks every hour. If we do not expect checks to fail, that may still be 6-12-fold more often than necessary. Or a check every 10 minutes is still “many checks per hour”, and yet does not blow up the traffic stats 10-fold more than necessary to get a “desirable” outcome.
There are also additional costs to consider when doing a check every minute: that is 1440 checks every 24 hours! Data must be stored, CPU time spent, waste heat is generated (it is not exactly exasperating climate change but it is not not doing that either!), etc. Whereas if a check every 10 minutes is used, then the same number of checks would span a 10-day timeframe. Depending on whatever else the machine is doing (gaming? other server checks?), it reduces the load 10-fold and something that much may even change things on a qualitative rather than merely quantitative basis.
Well, it was a thought for consideration at any rate.
Every one minute is really nothing
