-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
fix(performance-quick-trace-query): Using Sentry.captureException to inspect trace endpoint response. #58167
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
…inspect trace endpoint response.
@@ -73,6 +74,10 @@ export default function QuickTraceQuery({children, event, ...props}: QueryProps) | |||
organization | |||
); | |||
|
|||
const scope = new Sentry.Scope(); | |||
const traceErrorMsg = 'Trace endpoints returning non-array in response'; |
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.
Prob don't need a var here
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.
Will be getting rid of it all once I have some answers
traceTransactions, | ||
traceFullResults, | ||
}); | ||
Sentry.captureException(new Error(traceErrorMsg), scope); |
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're capturing this as an exception vs. a message it's fine (I usually just do message for exploratory work), but just watch the frontend errors once this is out, might trip an alert
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Addresses issues: issue1 and issue2.
Prevents issue details page from failing. When error is triggered, we just display a link to the trace view without the navigator nodes.