Hey there! I'm currently looking at the NGINX-opentracing documentation and have some questions about NGINX span inheritence.
My current issue is that NGINX keeps making new spans every time a request passes through, so my spans aren't chaining together into a single trace when I use an NGINX proxy for my second app.
I currently have;
trace_1: app_1_span, trace_2: nginx_span, trace_3: app_2_span
Where I'd like to have;
trace_1: app_1_span -> nginx_child_span -> app_2_span
If I want to propagate an active span from my app 1 calling app 2 (through an nginx proxy) would I just need to attach the
HTTP_UBER_TRACE_ID header to the request made by app 1? Will the
jaegertracing_plugin use this header to create a child span of the span created in app 1 when creating the NGINX span? (Apologies if that's a bit confusing) Does this sound a bit off, if so do are there any suggestions?
with master_span.tracer.start_span("foo"). This results in the spans appearing to be unrelated... I'm clearly missing something, but I'm not sure what it is. Could somebody point me in the right direction?