-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
help request: opentelemetry + grpc-transcode not working #9270
Comments
@shreemaan-abhishek help me talk a look |
On it. |
Note that open telemetry only supports binary-encoded OLTP over HTTP. So I wanted to know if you were using grpc-transcode to support OLTP over GRPC. |
@shreemaan-abhishek I was trying to get regular OTLP over HTTP traces, the GRPC transcoding was being used to reach GRPC services (User service, in this example) |
Thanks, I was able to reproduce this issue. Let me take a look for a fix. |
@kingluo, should we support this or it is by design? |
It's a bug. apisix/apisix/plugins/grpc-transcode/proto.lua Lines 100 to 102 in 1434335
Then in turn it discards the otel proto compiled at startup: |
Any progress on this issue, also facing open telemetry issues with the same reported error. |
When will this problem be repaired? Now it may affect me in production, and I feel sad about this. |
Yes, @kingluo Please take a look. :) |
@ThalysonR Please take a look. :) #9606 |
cc @coffeebe4code @Jamel-jun The bugfix was merged, please check. |
considered resolved |
Description
I've been testing apisix and tried using otel plugin while transcoding to grpc and got an error. I did try using the otel plugin with http and it works fine, so I assume the problem is with the 2 plugins working together. This is the error i got:
This is my config:
The transcoding part works fine, I'm able to get the expected response from the grpc service, just missing the otel trace.
Am I maybe using the plugins incorrectly?
Environment
apisix version
): 3.2.0 docker imageuname -a
): Ubuntu WSL2The text was updated successfully, but these errors were encountered: