Michael Nikitochkin

@esetnik here is release https://github.com/opentracing-contrib/nginx-opentracing/releases/tag/v0.11.0

I think you should create a location with regexp instead of variables to make it work. I try to find the person whom would contribute to the project.

@james-callahan Do you have an example how we can reproduce the problem?

Here is an example how you can compile Nginx opentracing with new Opentracing and Jaeger to support w3c format: https://github.com/opentracing-contrib/nginx-opentracing/pull/147/files

Here is my working Dockerfile to make work Nginx 1.19.5 with Opentracing 1.6.0 https://github.com/opentracing-contrib/nginx-opentracing/pull/143

Good catch. There is an example how opentelemetry-cpp could be built with nginx: https://github.com/kubernetes/ingress-nginx/pull/8585/files or https://github.com/iquirino/nginx-opentelemetry Here new question should it be in this repo? If not where the `nginx-opentelemetry`...

You can check how ingress-nginx is building: https://github.com/kubernetes/ingress-nginx/blob/main/images/nginx/rootfs/build.sh

@pauqilaz You are right. I would advice to obfuscate/drop tag in opentelemetry collector side. Another suggestion to move sensitive information from query to headers, just because of this. The url...

More about semantic convention of `http.url` in https://opentracing.io/specification/conventions/ http.url | string | URL of the request being handled in this segment of the trace, in standard URI format. E.g., "https://domain.net/path/to?resource=here"...

Contribution are welcome. There are no active developers that would work on it as far I know.