Lua.
Don't call the ambulance, it's too late for me
Haatveit
joined 1 year ago
We got warnings of this in my area, but we just barely missed the danger zone I guess. All we ended up with was a few days of steady rain. Seems it got a lot worse elsewhere...
Many laptops/ultrabooks have easily accessible batteries nowadays, any specific example when you mean sealed up?
These are all things that most phones already do, though. I think a realistic expectation of battery lifetime is needed here. Better allow for easier replacement in my opinion, the batteries themselves are not expensive (though we don't want to generate unnecessary waste, so, of course we try to make them last as long as feasible)
I can't give an authorative answer (not my domain), but I think there are two ways these types of things are done.
First is just observing the page or service as an external entity; basically requesting a page or hitting an endpoint, and just tracking whether you get a response (if not, it must be down), or for measuring load level in a very naive way, track the response time. This is easy in the sense that you need no special access to the target. But it's also limited in its accuracy.
Second way, like what your github example is doing, is having access to special api endpoints for (or direct access to) performance metrics. Since the github status page is literally ran by Github, they obviously have easy access to any metric they could want. They probably (certainly) run services whose entire job is to produce reliable data for their status page.
The minute details of each of these options is pretty open ended; many ways to do it.
Just my 5¢ as a non-web developer.