Skip to content

Conversation

@shuheiktgw
Copy link
Contributor

Description:
I've added support for the gRPC endpoint in jaeger_query_extension. I made it as backward-compatible as possible and decided not to expose the gRPC endpoint by default. However, if exposing it by default is acceptable, I’m happy to make those changes. Thanks for the review!

Link to tracking Issue(s):

Testing:

Documentation:

@shuheiktgw shuheiktgw requested a review from a team as a code owner September 28, 2025 07:39
@shuheiktgw shuheiktgw force-pushed the support_jaeger_query_grpc branch from 90ae6f5 to 3a60899 Compare September 28, 2025 11:20
@timonegk
Copy link

timonegk commented Nov 17, 2025

@shuheiktgw what's the state of this? Looks like a unit test is failing. Also maybe someone (@swiatekm ?) could review?

note: "Support gRPC endpoint for jaeger_query extension and expose it when configured."
issues: [4358]
subtext: |
- HTTP remains defaulted to 16686; gRPC has no default and is exposed only when `jaeger_query.grpc.endpoint` is set.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support grpc endpoint for jaeger_query_extension

3 participants