Skip to content
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: When integrating the OpenTelemetry (OTel) plugin with APISIX, is there a way to include APISIX in the trace based on the traceId and spanId from the request headers? #11990

Open
masaya87266 opened this issue Feb 24, 2025 · 0 comments
Labels
question label for questions asked by users

Comments

@masaya87266
Copy link

masaya87266 commented Feb 24, 2025

we have established end-to-end tracing from the frontend to APISIX and then to the backend. The desired outcome is for APISIX to receive the spanId from the frontend and incorporate it into the trace, and for the backend to receive the spanId from APISIX and incorporate it into the trace as well. However, currently, APISIX generates its own spanId. Is there a way to pass the spanId from the frontend instead?

Environment

  • APISIX version (run apisix version):
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):
@dosubot dosubot bot added the question label for questions asked by users label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question label for questions asked by users
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant