News for hackers. Stuff that matters.
Re:Self hosted uptime robot alternative written in go by zimpenfish on Wednesday November 11, 2020 @01:37PM (#25061309)
What always seems to be missing from these things is gRPC monitoring - there's a defined HealthCheck endpoint, even, specifically for this situation. Maybe people just don't run gRPC services as much as the hype would imply?
Re:Self hosted uptime robot alternative written in go by enz on Wednesday November 11, 2020 @03:50PM (#25062828)
Why would this be so valuable compared to basic HTTP health check?
Re:Self hosted uptime robot alternative written in go by zimpenfish on Wednesday November 11, 2020 @05:04PM (#25063567)
If you've got a gRPC API, you don't necessarily have anything serving HTTP that would correlate to that service - I know we don't, for example; the only HTTP is for serving static files, everything else is gRPC, and HTTP checks wouldn't spot any problems.
Re:Self hosted uptime robot alternative written in go by capableweb on Wednesday November 11, 2020 @05:25PM (#25063739)
Don't people usually use gRPC over HTTP?
Re:Self hosted uptime robot alternative written in go by zimpenfish on Thursday November 12, 2020 @12:34AM (#25066797)
The core protocol uses HTTP/2 as a transport, yes, but you'd have to convert the conceptual gRPC request to the protobuf-encoded version and somehow pass that to the HTTP/2 endpoint as a binary blob, then decode/match the binary blob you get back - which none of the status pingers really offer either.

(You could use `gRPC-web` to make JSON-encoded requests but you need specific support on the server end for that.)