-
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
bug: grpc-transcode cannot be used with opentelemetry #10460
Comments
could you please provide steps to reproduce? |
|
Can you help with more detailed information, if you do that, anyone wanting to investigate on this issue can quickly get started and find the bug then plan to fix it. You can share the configurations and the commands you used to make the setup where you found this bug. |
What do you mean by |
I turned off the OpenTelemetry plug -in and returned to normal |
@Jamel-jun please provide more detailed reproduction steps. |
@Jamel-jun any update? |
it is helpful if you share the code/text instead of screenshots. |
Current Behavior
grpc-transcode cannot be used with opentelemetry.
![image](https://private-user-images.githubusercontent.com/50609931/281368410-488e3698-284d-4af7-96b3-51f39e11c83f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIxODM1MjIsIm5iZiI6MTcyMjE4MzIyMiwicGF0aCI6Ii81MDYwOTkzMS8yODEzNjg0MTAtNDg4ZTM2OTgtMjg0ZC00YWY3LTk2YjMtNTFmMzllMTFjODNmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI4VDE2MTM0MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFhMDY3MWE1ODE0OWUzZmZiOWVlNDA0YzVmNmFlNmE4NTI2MGUwYTFiYjEwZDY5MjAwZjQ2ZDFjYWVhODU5NTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.SKvHBaQdpGgZcQCRGbvxwDHoD0dcDgdpNhTrS9M5n38)
The interface backend is grpc, and the frontend requests through http application/json type, after reaching apisix.
The OpenTelemetry plug-in sends the trace to otel, which is normal.
But the apisix return parameter is incorrect.
Expected Behavior
No response
Error Logs
No response
Steps to Reproduce
Environment
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: