-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(nextjs): Add transaction name to scope of server component #11850
Merged
Conversation
This file contains 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
size-limit report 📦
|
Leaving this here for the future: E.g. this trace: https://sentry-javascript-sdks.sentry.io/performance/trace/24883c2fb15b4ea28ce5787afacc577b/ which comes from the canary tests (I think) shows the root cause, I believe. A bunch of "unrelated" (??) component renders are in the same trace, probably clobbering up the transactionName on the isolationScope, I guess... 🤔 |
s1gr1d
changed the title
feat(nextjs): Add transaction name to isolation scope when page or layout
feat(nextjs): Add transaction name to isolation scope only when not defined
Apr 30, 2024
s1gr1d
changed the title
feat(nextjs): Add transaction name to isolation scope only when not defined
feat(nextjs): Add transaction name to scope
May 2, 2024
s1gr1d
changed the title
feat(nextjs): Add transaction name to scope
feat(nextjs): Add transaction name to scope of server component
May 2, 2024
mydea
reviewed
May 2, 2024
Co-authored-by: Francesco Novy <[email protected]>
mydea
approved these changes
May 2, 2024
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.
ref #11782