Add middleware to detect jaeger trace context over HTTP#3325
Merged
Add middleware to detect jaeger trace context over HTTP#3325
Conversation
Collaborator
|
Why wouldn't this go in |
Contributor
Author
I didn't think this was possible initially; I've worked out how to do it now! |
leth
force-pushed
the
trace-context-detect
branch
from
c452f31 to
e8eb7af
Compare
leth
force-pushed
the
trace-context-detect
branch
from
e8eb7af to
67b887c
Compare
bboreham
approved these changes
Aug 28, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Previously scope would not honor http headers requesting that a request be traced.
Updates weaveworks/common to d442d08d89b51712ca61de3f7c14e2e218a739d7