Distributed Tracing gRPC for remote client and server #3099
Unanswered
chhunsocheat
asked this question in
Q&A
Replies: 1 comment
-
I'm not sure I get your point on "the gRPC client and gRPC server are using the same trace configuration and they both hosted on the same server". The example is suggesting running the client and server in two separate Node.js processes, as said in the README. For trace context propagation, the grpc instrumentation injects the necessary information in the grpc metadata: https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/packages/opentelemetry-instrumentation-grpc/src/grpc-js/clientUtils.ts#L229. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to implement distributed tracing in gRPC. In this grpc-js example, the gRPC client and gRPC server are using the same trace configuration and they both hosted on the same server. However, my gRPC client and server sit in a different hosting server, meaning they have to communicate remotely. When I was trying to follow the example grpc-js, the context from the gRPC client does not get passed to the gRPC server. Is there anyway to solve this or I am just implementing it wrong?
Beta Was this translation helpful? Give feedback.
All reactions