Hello, I'm seeing two Traceparent headers on requests coming out of an OBI-instrumented reverse proxy, similar to this issue: #976 Requests forwarded by the proxy have an OBI-generated traceparent in addition to the traceparent of the incoming request.
I first encountered this by running Beyla on a newly scaffolded Rails app, which used the Thruster reverse proxy running in the same container as the app webserver. When I replaced Thruster with Caddy, header was not duplicated.
Reproduced using a Go reverse proxy: https://github.com/kessl/obi-duplicate-traceparent
Hello, I'm seeing two
Traceparentheaders on requests coming out of an OBI-instrumented reverse proxy, similar to this issue: #976 Requests forwarded by the proxy have an OBI-generated traceparent in addition to the traceparent of the incoming request.I first encountered this by running Beyla on a newly scaffolded Rails app, which used the Thruster reverse proxy running in the same container as the app webserver. When I replaced Thruster with Caddy, header was not duplicated.
Reproduced using a Go reverse proxy: https://github.com/kessl/obi-duplicate-traceparent