-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
feat(replay): query IP for trace connected errors for replay summary (v2) #98479
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 comment was marked as off-topic.
This comment was marked as off-topic.
0e2b665
to
345fddc
Compare
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.
🤞
Branching off this and adding better tracing/logging to debug |
Wrap the methods of this endpoint with a custom transaction. Sampling rates will be options-controlled. We need a high POST sample rate while we develop this feature, to debug slow loading times. I believe options can be segmented by user email, or something like is_employee - will experiment Merge with #98479
|
||
# Process issuePlatform query results | ||
if issue_query_results and "data" in issue_query_results: |
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 there a chance the query results don't exist?
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 that's only when snuba errors, and we should raise rather than silently skip
redo of #97737
reverted the old pr as the trace id query was too slow -- it did 2 snuba queries per trace id (bad). this pr instead makes it 2 total queries for all trace ids
MERGE WED