Use OpenTelemetry SDK in HotROD

[rbroggi]

• replacing the jaeger-client-go ot tracer implementation with the ot-otel bridge implementation

Signed-off-by: rbroggi ro_broggi@hotmail.com

Which problem is this PR solving?

• Issue Upgrade HotROD example to use OpenTelemetry SDK #3380

Short description of the changes

• First iteration in replacing the jaeger client ot tracer implementation with the otel bridge ot implementation

[codecov]

Codecov Report

Base: 96.51% // Head: 96.48% // Decreases project coverage by -0.03% ⚠️

Coverage data is based on head (84e7663) compared to base (9d4d4cd).
Patch has no changes to coverable lines.

❗ Current head 84e7663 differs from pull request most recent head d8f4543. Consider uploading reports for the commit d8f4543 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3390      +/-   ##
==========================================
- Coverage   96.51%   96.48%   -0.03%     
==========================================
  Files         260      260              
  Lines       15215    15215              
==========================================
- Hits        14684    14680       -4     
- Misses        449      452       +3     
- Partials       82       83       +1     

Impacted Files	Coverage Δ
pkg/config/tlscfg/cert_watcher.go	92.63% <0.00%> (-2.11%)	⬇️
cmd/query/app/server.go	94.11% <0.00%> (-1.48%)	⬇️
cmd/collector/app/server/zipkin.go	70.73% <0.00%> (+2.43%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[yurishkuro]

jaeger-ui submodule update should not be in this PR, please make sure to rebase off master

[rbroggi]

Some comments:

With this change something is not really going as planned as the DAG I get is:

instead of the one in the article

Another change that will have to be documented is that we also need to open the grpc port while running the all-in-one container for the go binary to reach jaeger:

docker run -d -p6831:6831/udp -p16686:16686 -p14268:14268 jaegertracing/all-in-one:latest

Will there be a way to update the medium article (it was very useful to me, it would be a shame to loose it)

[rbroggi]

The frontend tracers are not connecting to the rest:

[rbroggi]

The frontend tracers are not connecting to the rest:

Dear @yurishkuro, would you have any advice on how I could troubleshoot this problem efficiently?

By investigating the code I fail to understand why this change had an impact only in the frontend component of the HOTRod. Well I'm not even sure whether the problem lies 100% on the frontend, the only real info I have is that there is a discontinuity between the trace from frontend and the others.

[yurishkuro]

I suspect this has something to do with the propagator of the context on the wire. What happens when the code calls tracer.Inject() and the tracer is the one from the bridge?

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You may re-open it if you need more time.

[stale]

This pull request has been automatically closed due to inactivity. You may re-open it if you need more time. We really appreciate your contribution and we are sorry that this has not been completed.

[yurishkuro]

This was finished in #4187