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

Proxy filter to propagate Openzipkin b3 headers #578

Closed
samutamm opened this issue Apr 8, 2022 · 0 comments · Fixed by #579
Closed

Proxy filter to propagate Openzipkin b3 headers #578

samutamm opened this issue Apr 8, 2022 · 0 comments · Fixed by #579

Comments

@samutamm
Copy link
Contributor

samutamm commented Apr 8, 2022

Is your feature request related to a problem? Please describe.
Easegress supports sending tracing spans per request to Zipkin tracing system. These spans can help to troubleshoot latency problems in the downstream back-end systems that Easegress pipelines connect to.

Though sometimes the span information comes in incoming requests in b3-propagation headers and it should be passed along to the downstream back-ends. Currently Easegress does not propagate these headers.

Describe the solution you'd like
When b3 headers are present, propagate them in the Proxy filter to the downstream back-end servers, as desribed in https://github.com/openzipkin/b3-propagation . If b3 headers are not present, generate a new span and inject to it to the header.

Describe alternatives you've considered

Additional context


Thanks for contributing 🎉!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant