Improve troubleshooting with jaeger

[or-adar]

Hi! I'm trying to enable telemetry for certain components in NSM architechture to be able to troubleshoot my setup more easily with Jaeger. However, for some reason, it looks like spans in Jaeger appear as separate while a request can involve more than one service, making it harder to troubleshoot the flow of different requests.

I've enabled telemetry for NSC, nsmgr and forwarders for my setup. As for my scenario, I have a NSC sending a grpc Reqest call to NSMgr to open a vWire, for my scenario, this call is expected to fail and emit an error with message "all forwarders have failed", up to here everything is good, but what I'm trying to understand is - why not all consequent requests and dependant services get correlated with the initial request of my NSC when I view the span for my NSC grpc Request? the traceID isn't being propogated?

[glazychev-art]

Hi @or-adar, Thanks for the report! It looks like we fixed a few problems with opentelemetry (here). Could you please check it on v1.9.0-rc.1?