bee
bee copied to clipboard
OpenTracing spans in the retrieval protocol are wrong
We're apparently creating too many spans and their nesting order is wrong when looking in jaeger. It can be further simplified and needs a cleanup.
Also note the empty spans that get created even though a request is not issued.
