-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
feat(replays): switch to replay_id column from tag #68950
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
Changes from all commits
0bb3b62
824d4a8
8666d0c
8fd586e
9acd5e9
4e06bce
af751e6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -742,8 +742,20 @@ class Columns(Enum): | |
REPLAY_ID = Column( | ||
group_name=None, | ||
event_name="replay_id", | ||
transaction_name=None, | ||
discover_name=None, | ||
transaction_name="replay_id", | ||
discover_name="replay_id", | ||
issue_platform_name="replay_id", | ||
alias="replay.id", | ||
) | ||
# We used to set the replay_id as a tag on error events as | ||
# replayId. We allow this query for backwards compatibility, | ||
# but in the future shouldn't be displayed in the UI anywhere | ||
# as a suggested column. | ||
REPLAY_ID_DEPRECATED = Column( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Where is this used? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Because this was exposed to discover/dashboards, you'll want to make sure it's not being used by customers if you were to remove it. |
||
group_name=None, | ||
event_name="replay_id", | ||
transaction_name="replay_id", | ||
discover_name="replay_id", | ||
issue_platform_name="replay_id", | ||
alias="replayId", | ||
) | ||
|
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.
Just checking we actually write to this col from issue platform?
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.
yup https://github.com/getsentry/snuba/blob/8d4ea6917d5efef88fafe5ca33814dbf91d02595/snuba/datasets/processors/search_issues_processor.py#L203
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.
Ok - so as long as it's in the context for the event we pass to snuba it should work...
Are replays associated to transactions? If so, then perf issues from transactions should work automatically. Other issue platform types that make a "synthetic" event would need to explicitly include it there
Uh oh!
There was an error while loading. Please reload this page.
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.
yup, replays are associated to transactions. its done via the dynamic sampling context, which then adds the replay context in relay. and for others:
rage click issue:
sentry/src/sentry/replays/usecases/ingest/issue_creation.py
Line 90 in 8666d0c
feedback issue:
sentry/src/sentry/feedback/usecases/create_feedback.py
Line 98 in 8666d0c
Crons
-- not applicable
that should be everything