-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
fix: Clarify error level impact on sessions #15198
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
Clarify in the develop docs that only events with level error or higher must mark sessions as errored.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Co-authored-by: philipp.hofmann <philipp.hofmann@sentry.io>
Co-authored-by: philipp.hofmann <philipp.hofmann@sentry.io>
Co-authored-by: philipp.hofmann <philipp.hofmann@sentry.io>
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.
maybe it's just my style, but i'd love to also see like a table of all the related factors so i can see which properties affect session status, but also which properties do not.
Something like this:
| method | level | hasStacktrace | resulting session status |
|---|---|---|---|
| captureException | error |
false or true |
error |
| etc... |
|
I added a table, @ryan953, is it clearer now? |
DESCRIBE YOUR PR
Clarify in the develop docs that only events with level error or higher must mark sessions as errored.
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: