David Goffredo

I might patch this. Full support would mean adding Alpine to our CI, which I'd say is not worthwhile for this soon-to-be-deprecated project. But a patch release wouldn't hurt.

I was looking at this PR. Checked out the branch, and ran `./check_envoy_configs.sh` in `examples/envoy-tracing/`. It hanged after the following error: ``` Creating envoy-tracing_dd-agent_1 ... done Creating envoy-tracing_envoy-v1.13_1 ... done...

Hi, Marc. I don't have an example of using `DD_TRACE_SAMPLING_RULES` (or the equivalent `dd-config.json`) to configure sampling rules for multiple services in the nginx ingress controller for kubernetes. It would...

Ooo, look at that. Yes, `opentracing_tag service.name` will set the service name on the "current span," which if `opentracing_trace_locations on` means the _location span_. The outer _request span_ will be...

Might as well keep this open. It's something I'd like to support.

None, I'm afraid. My time has been spent on getting the new tracing library into Envoy and on other internal designs. Work is planned to add the new tracing library...

I should also point out that getting the new code into the ingress controller is a separate project, also planned, but that will take longer. Ideally we'd figure out a...

I had a theory about why this might be happening, but it's wrong. It would be helpful to have the incoming request headers for a request that produces the error...

I attempted a reproduction but was unable to get nginx to produce that error message.

The issue might be that the Datadog tracing library used by ingress-nginx, [dd-opentracing-cpp][1], does not understand the `DD_TRACE_PROPAGATION_STYLE_EXTRACT` environment variable. It understands only `DD_PROPAGATION_STYLE_EXTRACT` and `DD_PROPAGATION_STYLE_INJECT` (note the lack of...