-
Notifications
You must be signed in to change notification settings - Fork 98
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
Can't get gRPC Context Client to Server to match #434
Comments
We currently propagate distributed context using an http header meaning that distributed tracing will only work over http for now. We are designing an alternate mechanism for grpc (likely using http://www.grpc.io/docs/guides/concepts.html#metadata) but need to coordinate between different language trace agents (we want to ensure a request sent from a Node.js grpc client to a go grpc server will handle context correctly). |
I've opened #436 to address this by writing trace context to gRPC metadata. While this field isn't standardized for other Cloud Trace clients, it should provide distributed tracing for Node.js microservices. |
Hi @ethanrubio, we just release version 1.0.1 which includes the PR mentioned above. Please give it a try when you have the time and feel free to re-open this issue if there are any problems! |
@kjin Thanks again for adding this! Is it possible to search/filter for |
The value of |
I'm trying to use this library to trace gRPC and Hapi requests throughout a small microservice environment.
There are three services (using a combo of gRPC and HapI) that I'm trying to log correctly in StackDriver Trace. I started all three services under the same project, but on StackDriver, I'm unable to link up the gRPC Client requests with the gRPC Server handling. However, a service with gRPC making HTTP requests to a Hapi server are correctly matched up on the web interface.
Any insights would be greatly appreciated! Thanks!
The text was updated successfully, but these errors were encountered: