feat(nextjs): Continue trace using incoming sentry-trace header
#3587
Conversation
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
Contributor
size-limit report
|
kamilogorek
approved these changes
May 24, 2021
lobsterkatie
force-pushed
the
kmclb-nextjs-serverside-performance-cleanup
branch
from
1bd25dc to
e73c241
Compare
Base automatically changed from
kmclb-nextjs-serverside-performance-cleanup
to
kmclb-next-js-performance
May 25, 2021 14:23
lobsterkatie
force-pushed
the
kmclb-nextjs-continue-transaction-from-headers
branch
from
d541a24 to
411420d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support for continuing a trace started in another service, by reading and applying the
sentry-traceheader on incoming requests. It also passes the request as extra context in thetracesSampler.