-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(node): Add docs for server side release health #3541
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
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sentry/sentry-docs/53ugdR8qESSsSmcncnGLfhiM6YNy |
|
We should be able to use |
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
PeloWriter
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.
I think we may have duplicated information on the page (lines 5 and 36, lines 9 and 38). If so, we should have that content as a separate section that introduces what we capture, then cover client v. server side.
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
| We create a session for every page load. For single-page applications, we will create a new session for every navigation change (History API). | ||
| ### Browser-side | ||
|
|
||
| We create a session for every page load. For single-page applications, we will create a new session for every navigation change (History API). |
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.
Suggest we link to the content for the History API.
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
src/includes/configuration/auto-session-tracking/javascript.mdx
Outdated
Show resolved
Hide resolved
| We mark the session as an error if the SDK captures an event that contains an exception (this includes manually captured errors). | ||
| We mark the session as an error if the SDK captures an event that contains an exception (this includes manually captured errors). | ||
|
|
||
| By default, the JavaScript SDKs are sending sessions, to disable this toggle the flag `autoSessionTracking` to `false`: |
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.
Isn't this already stated on line 9?
| We mark the session as crashed if an _unhandled error_ or _unhandled promise rejection_ bubbled up to the global handler. | ||
|
|
||
| We mark the session as an error if the SDK captures an event that contains an exception (this includes manually captured errors). | ||
| We mark the session as an error if the SDK captures an event that contains an exception (this includes manually captured errors). |
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.
is this a duplicate of line 5?
Co-authored-by: Fiona <[email protected]> Co-authored-by: iker barriocanal <[email protected]>
This PR: