Fix OpenTracing context propagation in Swarm internal APIs #1181

nonsense · 2019-01-31T16:24:40Z

At the moment if you send a GET request to Swarm for a specific content, you don't get proper tracing information in Jaeger, because the context propagation is broken.

We need to fix this, so that we can see detailed traces of specific GET (or POST) requests and compare fast requests to slow requests in order to understand why we have a high variance for upload/download in smoke tests.

Related to: #1152

nolash mentioned this issue Jan 31, 2019

network: clean shutdown for Fetcher is impossible #1148

Closed

nolash self-assigned this Jan 31, 2019

nolash added bug network labels Jan 31, 2019

nolash mentioned this issue Feb 1, 2019

swarm/network, swarm/storage: Preserve opentracing contexts #1182

Closed

This was referenced Feb 8, 2019

swarm/network, swarm/storage: Preserve opentracing contexts ethereum/go-ethereum#19022

Merged

swarm/network: Keep span across roundtrip #1210

Closed

nolash mentioned this issue Feb 20, 2019

swarm/network: Keep span across roundtrip ethereum/go-ethereum#19140

Merged

adamschmideg added this to the 0.3.12 milestone Feb 21, 2019

nonsense self-assigned this Mar 20, 2019

nonsense unassigned nonsense and nolash Mar 21, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix OpenTracing context propagation in Swarm internal APIs #1181

Fix OpenTracing context propagation in Swarm internal APIs #1181

nonsense commented Jan 31, 2019 •

edited

Loading

Fix OpenTracing context propagation in Swarm internal APIs #1181

Fix OpenTracing context propagation in Swarm internal APIs #1181

Comments

nonsense commented Jan 31, 2019 • edited Loading

nonsense commented Jan 31, 2019 •

edited

Loading