🍋 LemMon - Lemmy Monitor - Servers Status

jmbreuer , 11 months ago

How about adding lemmy.ml?

It doesn’t have the same problem as lemmy.fhmy.ml, but especially because of current unknowns around .ml domains, it would benefit greatly from independent monitoring.

null OP , 11 months ago

Added 😀

kavin , 11 months ago

Would you like to add feddit.rocks? It’s a lemmy instance run by me :)

SuperSpaceFan , 11 months ago

Can you add Lemm.ee and Geddit.social?

null OP , 11 months ago

Wut? Lemm.ee was there since i announced this post 😀

Geddit.social maybe later will add.

SuperSpaceFan , 11 months ago

Oh okay, I see Lemm.ee now after doing a page refresh. Thanks

Coelacanth , 11 months ago

Can you add feddit.nu?

Ludrol , 11 months ago

Can you add szmer.info?

SleepingInTraffic , 11 months ago

Great tool! Any chance of feddit.uk?

HamSwagwich , 11 months ago

Showeq.com please!

Paralda , 11 months ago

Can you add programming.dev?

null OP , 11 months ago

Added 😀

chrisbit , 11 months ago

Please add cocte.au and leminal.space

lnxtx , 11 months ago

feddit.nl 🙏

SoNick , 11 months ago

@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!

infamousbelgian , 11 months ago

Please add waste-of.space. Thnx!

sabreW4K3 , 11 months ago

Add Lemmy.tf please

OpenStars , 11 months ago

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?

Wintermute , 11 months ago

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.

Shadow , 11 months ago

You made me curious. Since midnight lemmy.ca has averaged 110 requests per second, with multiple periods of doing ~3000 request/sec.

1 request every minute is nothing :)

rideranton , 11 months ago

A single health check call a minute by a single app is nothing compared to real world usage

OpenStars , 11 months ago

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.

null OP , 11 months ago

Every one minute is really nothing

Agility0971 , 11 months ago

why not uptime-kuma?

mosiacmango , 11 months ago

This looks like a fork of it.

null OP , 11 months ago

You are totally wrong here

null OP , 11 months ago

Because i dont like uptime-kuma and i know how to write a code 😜

Zelaf , 11 months ago

Best answer. Really like your UI design! (I like uptime-kuma tho)