-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat: Add custom distributed tracing docs for JS/Node #8469
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
95df29f to
8805616
Compare
lforst
left a comment
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.
Sorry for big review. I wanted to use the opportunity to clean this up in general.
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
| - Inject tracing information to the outgoing request when sending outgoing requests. | ||
|
|
||
| To learn more, see our <PlatformLink to="/distributed-tracing/">Distributed Tracing</PlatformLink> docs. | ||
| To learn more, see our <PlatformLink to="/usage/distributed-tracing/">Distributed Tracing</PlatformLink> docs. |
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.
I feel conflicted about having these two pages 🤔 Or rather about linking back to that page here. People are here for manual instrumentation. Why should we link back to auto-instrumentation. I think we should either delete this line or link to the auto-instrumentation all the way at the top of this page in-case people got lost.
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.
I think the idea of this is that on that page we describe distributed tracing as a concept, generally 🤔 (I copied this from other existing pages for custom instrumentation, FWIW)
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.
@mydea - I agree that's the point of the link. Ideally, conceptual information and how-to information should be separate, which would make this less confusing. As it is, I think the link is ok though.
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| ## Enabling Distributed Tracing without `Http` Integration | ||
|
|
||
| If you do not want to use the `Http` integration in conjuction with `tracing: true`, you can manually extract and inject tracing information into your application. For this, you must: |
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.
| If you do not want to use the `Http` integration in conjuction with `tracing: true`, you can manually extract and inject tracing information into your application. For this, you must: | |
| If you do not want to use the `Http` or `Undici` integrations, you can manually trace your application. For this, you must: |
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/node.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/node.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Luca Forstner <[email protected]>
shanamatthews
left a comment
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.
Ok from my end, once you fix the formatting issues I commented on.
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/node.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/node.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/how-to-use/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/distributed-tracing/custom-instrumentation/node.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Shana Matthews <[email protected]>
Lms24
left a comment
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.
LGTM!
src/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Lukas Stracke <[email protected]>
This adds docs for custom distributed tracing for Node & Browser JavaScript, including the new
continueTracemethod, which was added here: getsentry/sentry-javascript#9164.We do not show this for Next, Remix, Sveltekit and Astro - not 100% sure if this is correct, or if there are other guides where we should/should not show this.