-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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(tracing-without-performance): Returned orphan errors with trace … #54103
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #54103 +/- ##
==========================================
- Coverage 79.60% 79.60% -0.01%
==========================================
Files 4983 4983
Lines 210531 210543 +12
Branches 35846 35851 +5
==========================================
+ Hits 167593 167597 +4
- Misses 37795 37801 +6
- Partials 5143 5145 +2
|
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.
Aside from my suggestion to minimize passed params, looks good 👍
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.
+1 to Kevan's comment. Nice changes!
…g number of params being passed to serializer.
Suspect IssuesThis pull request has been deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
For the ticket: https://getsentry.atlassian.net/browse/PERF-2052.
We want to add new rows to trace views for traces that contain orphan errors. Currently the trace endpoint ignores orphan errors.
This PR aims to append orphan errors to the response of the trace endpoint and should work for both scenarios:
Returning
event_type:"error"
andgeneration:0
with all errors, to help us identify the orphan errors in the frontend and always group them under the first generation.Added tests for both scenarios.