-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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(perf): Requests module SDK instrumentation documentation #9963
Conversation
Instead of repeating ourselves, link to the full documentation.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bundle ReportChanges will increase total bundle size by 527 bytes ⬆️
|
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.
A couple small optional suggestions.
span?.setAttribute('server.address', parsedURL.hostname); | ||
span?.setAttribute('server.port', parsedURL.port || undefined); | ||
|
||
span?.setAttribute('http.response.status_code', response.status); |
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 like the use of optional chaining 👍 makes me question why I used an if
statement in my docs.
@@ -21,24 +21,15 @@ On the [**Requests** page](#requests-page), you get an overview of the domains t | |||
></iframe> | |||
</div> | |||
|
|||
## Prerequisites | |||
## Prerequisites and Limitations | |||
|
|||
<Note> | |||
Network requests using non-HTTP protocols (FTP, WebSocket, etc.) are not supported at this time. | |||
</Note> | |||
|
|||
Availability of HTTP request monitoring depends on the SDK your application uses. In most cases, Sentry's SDKs automatically enable HTTP request tracking. You can check your SDK's <PlatformLink to="/performance/instrumentation/automatic-instrumentation">automatic instrumentation documentation</PlatformLink> to see if it includes tracking HTTP requests. | |||
|
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.
NIt, I might add a heading "Custom Instrumentation" to draw people's attention to this option.
Also, worth a discussion about whether we should suggest setting network.protoco.name
, network.protocol.version
, if people try to instrument an HTTP/2 connection?
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 can add this to our span data conventions!
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!! Thanks for adding.
docs/platforms/javascript/common/performance/instrumentation/requests-module.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/javascript/common/performance/instrumentation/requests-module.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/python/performance/instrumentation/requests-module.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/python/performance/instrumentation/requests-module.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Liza Mock <liza.mock@sentry.io>
Co-authored-by: Liza Mock <liza.mock@sentry.io>
Co-authored-by: Liza Mock <liza.mock@sentry.io>
Co-authored-by: Liza Mock <liza.mock@sentry.io>
Co-authored-by: Liza Mock <liza.mock@sentry.io>
* Link to custom instrumentation docs * Add JavaScript platform docs * Add Python platform docs --------- Co-authored-by: Liza Mock <liza.mock@sentry.io>
I'm following the template set up for the Caches documentation! Adding manual instrumentation docs for JavaScript and Python, and linking to the snippets from the module documentation. Very similar to #9926