Open longility opened 3 years ago
You do have the right expectation. I'm looking into this now.
Thank you @dyladan . Let me know if you need more info or need me to try something.
Are you sure you're using the right grpc plugin? We have plugins for grpc
and for grpc-js
which are different modules
I believe so. You can verify as I have my package dependencies shown in comment above. Here is a more slim version:
//package.json
{ "dependencies": {
"@grpc/grpc-js": "^1.1.8",
"@opentelemetry/plugin-grpc-js": "^0.12.0"
} }
and in logs it shows this PluginLoader#load: trying to load @grpc/grpc-js@1.1.8
and doesn't error after that line.
ok great thanks.
Here is a slimmed down configuration that I have.
I'm using apollo as my gateway and making grpc clients to my microservices. I do have other metadata that I'm adding manually, which I don't think should matter.
Expectation I do not have to manually set metadata/headers for the grpc client when making calls. It should be automatic.
Actual I don't see any trace context on my gRPC server when checking request headers. I tested by manually adding the trace context using
span.context()
to get the data to pass as metadata, and it showed up.Do I have the right expectation? Is there something I should try that I may have missed? How can I debug further? Thoughts?