-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
ref(js): Rewrite outdated "Transaction Name" documentation #12091
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
99ec67e
to
e5d3f66
Compare
Bundle ReportChanges will decrease total bundle size by 270 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
|
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this! Left a few comments.
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
platform-includes/performance/beforeNavigate-example/javascript.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good write-up 🙌
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Liza Mock <[email protected]>
…name/index.mdx Co-authored-by: Liza Mock <[email protected]>
e046798
to
fc3fe31
Compare
DESCRIBE YOUR PR
This PR rewrites the "Enriching Events"->"Transaction Name" page which is was fairly outdated and misleading for JavaScript.
Most importantly, it now mentions that
scope.setTransactionName
only applies to error events and has nothing to do with spans and root span names. The page now disambiguates the two concepts and lists ways how to update both names individually.As an experiment, I added a "Further Information" section at the bottom of the page which tries to explain the historic context of why these two names are convoluted and appear ambiguous. I'm happy to remove this but this question and the confusion around the two names is coming up repeatedly on GitHub, in Discord as well as internally. While reviewing, feel free to let me know your thoughts if we should keep the section or reword it.
I decided to rewrite this page while triaging an older issue in the SDK repo where the two names were mixed up multiple times.
closes getsentry/sentry-javascript#13391
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES