Fix Rack http_server.queue spans missing from distributed traces #709
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a Rack application was on the receiving end of a distributed trace (e.g. 2nd service in chain), and it had enabled
request_queuing
, then thehttp_server.queue
span did not receive the distributed trace ID and parent ID because it was processed before distributed tracing was. The span would instead end up in its own trace.This pull request moves the distributed tracing operation to the top, so
http_server.queue
spans end up with the correct distributed tracing metadata, and are included into the trace.