Support grpc endpoint for jaeger_query_extension

[timonegk]

Component(s)

collector

Is your feature request related to a problem? Please describe.

jaeger_query_extension currently only exposes the http endpoint of jaeger_query as a service. Since jaeger_query also supports grpc (port 16685 by default), this endpoint should also be exposed if it is configured.

Describe the solution you'd like

The endpoint should be exposed in the same manner as the HTTP endpoint

Describe alternatives you've considered

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[frzifus]

Its part of the jaeger distrbution?

Ive no objections wdyt @open-telemetry/operator-approvers ?

[swiatekm]

I agree. We already support this extension, so we should support both ports.

[frittentheke]

I agree. We already support this extension, so we should support both ports.

And likely it makes sense to even expose gRPC on port 16685 by default?
Kinda like in the config docs here ... https://www.jaegertracing.io/docs/2.10/deployment/configuration/#jaeger-query and the in-code defaults at https://github.com/jaegertracing/jaeger/blob/832d9d82e166e481239294ecb6b704e570c22cbd/cmd/query/app/flags.go#L203-L216

[shuheiktgw]

👋 Hi team, can I work on it?