So I've got a home server that's having issues with services flapping and I'm trying to figure out what toolchain would be actually useful for telling me why it's happening, and not just when it happened.
Using UptimeKuma, and it's happy enough to tell me that it couldn't connect or a 503 happened or whatever, but that's kinda useless because the service is essentially immediately working by the time I get the notice.
What tooling would be a little more detailed in to the why, so I can determine the fault and fix it?
I'm not sure if it's the ISP, something in my networking configuration, something on the home server, a bad cable, or whatever because I see nothing in logs related to the application or the underlying host that would indicate anything even happened.
It's also not EVERY service on the server at once, but rather just one or two while the other pile doesn't alert.
In sort: it's annoying and I'm not really making headway for something that can do a better job at root-cause-ing what's going on.
Linux was the NFT or Blockchain or AI of 1999, so every tech company was jumping on board.
The sales pitch, as I remember, was that you could run your Wordperfect or CorelDraw shit on it, and not need to have Windows to use it and instead could join the future, which was Linux. Though, amusingly, their version of the future was running Windows binaries via Wine on Linux which, eh, okay but...
Of course, nobody used Wordperfect or CorelDraw at that point in history so I'm not entirely sure how that was supposed to sell you on buying not-Word and not-Photoshop.