-
Notifications
You must be signed in to change notification settings - Fork 345
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change query service portname to 'http-query' #909
Conversation
Signed-off-by: Gary Brown <gary@brownuk.com>
Should we also have a look at collector. The collector ports might have the same issues e.g. zipkin and Jaeger |
@pavolloffay Collector (grpc) is already fine, not sure we would want to expose the zipkin port? If that is a requirement it could be addressed as a separate issue. |
For instance to collect data from clients which makes sense bc zipkin supports large ecosystem of js-client libraries. |
Good point - I'll submit another PR soon. |
I had actually just opened a PR to fix this issue but I shall close it off given this PR now exists. I hope no-one takes offence but I thought the following worth mentioning. I would caution that the current PR doesn't take account of when the port is secured, e.g. 443/https. In my own PR I was calling a function as follows:-
I think it would make sense to have something similar added to this PR. A couple of additional For reference the closed PR is #912 |
@andye2004 Thanks for following up on this - would you mind rebasing your PR to add this change? |
Signed-off-by: Andy Elliott <andye@yambay.com>
Resolves #907
Signed-off-by: Gary Brown gary@brownuk.com