Add DialOptions field to Config struct #168
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Megrez Lu [email protected]
Resolve issue #166
Motivation
In order to connect the inter-process traces between implementations of
go-plugin
and its peer services, we have to inject the existing tracing context from the client side while extracting context should also be done from the server side.Design
Server Side
No necessary since we can already do the following, (excerpted from
jaeger
plugin from our private repository)Client Side
The only possibility to inject the tracing context is to add
grpc.UnaryClientInterceptor
orgrpc.StreamClientInterceptor
as an extraDialOption
following the idea fromgrpc-opentracing
,https://github.com/grpc-ecosystem/grpc-opentracing/blob/master/go/otgrpc/client.go
Comments
I am not sure about the
Broker
module.