New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom HTTP health check endpoint path #2572
Comments
This sounds like a reasonable request. I'm not actually sure what the best way to accomplish this is... we might need a new |
I already thought about that while implementing the PR but didn't come up with a nice solution and then lost track somehow. My idea was some kind of nested functional option, but I think your solution looks nicer than |
@johanbrandhorst @brumhard those are indeed the two solutions I would have suggested myself 馃憤 Imho functional options may be overkill to simply apply a non-default endpoint path in this case, so I would favor more the idea of having a
@brumhard that would be awesome, thank you 馃槃 ofc I'm also available to give it a try myself if you prefer 馃憤 In that case, I'll try to take care of it according to your preferences on the above and ping you guys in review. |
@antonioiubatti93 sry was a bit afk last week but glad that you got it working to your needs 馃憤馃徎 |
@brumhard no problem, I had actually very little to do, the base feature was very nice already 馃槃 |
馃殌 Feature
Thank you @brumhard and @johanbrandhorst for having the following HTTP health check endpoint available through the gRPC gateway, this is very useful 馃帀
WithHealthzEndpoint
asServeMuxOption
to register a/healthz
endpoint聽#2319To further enhance that, I would suggest to customize the endpoint path in order to use any path other than
/healthz
, so that any existing health check endpoints shall not undergo any disruption.The text was updated successfully, but these errors were encountered: