Report correct length for trace span #435
Merged
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.
The trace span in the
TracingMiddleware
should be the length it takes to return a response. Unfortunately because our Response body is a closure that will write the body at a later point and not the actual body we have not written the response body to the channel by the time we end the span in theTracingMiddleware
.To fix this I am manually starting and ending the span myself instead of using
withSpan
. TheTracingMiddleware
returns a response body that ends the span once the body has been written.Another issue arises if I leave this as is though. Someone could drop the response body which was returned by the
TracingMiddleware
and thespan.end
would never be called. To get around this I have wrapped it in a small class which will callspan.end()
ondeinit
, if it hasn't already been called.