Skip to content
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

chore(replay): ff to test reduced timeout for rage/dead clicks #77284

Merged
merged 2 commits into from
Sep 10, 2024

Conversation

aliu39
Copy link
Member

@aliu39 aliu39 commented Sep 10, 2024

This timeout is in dom_index.py (7000ms) and is the time we wait for dom changes before reporting a rage or dead click.

Trying out 5s instead of 7 for sentry orgs. Slack thread: https://sentry.slack.com/archives/C03USURCFBJ/p1725645076151569

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Sep 10, 2024
@aliu39 aliu39 requested a review from a team September 10, 2024 21:55
@aliu39 aliu39 enabled auto-merge (squash) September 10, 2024 22:05
@aliu39 aliu39 merged commit c8915fe into master Sep 10, 2024
49 checks passed
@aliu39 aliu39 deleted the aliu/rage-timeout-ff branch September 10, 2024 22:46
@@ -399,6 +399,8 @@ def register_temporary_features(manager: FeatureManager):
manager.add("organizations:session-replay-new-event-counts", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=False)
# Enable Rage Click Issue Creation In Recording Consumer
manager.add("organizations:session-replay-rage-click-issue-creation", OrganizationFeature, FeatureHandlerStrategy.INTERNAL, api_expose=False)
# Enable a reduced timeout when waiting for the DOM, before reporting Rage and Dead clicks
manager.add("organizations:session-replay-dead-click-reduced-timeout", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, default=False, api_expose=False)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realize I'm too late, but could the timeout be set in the option itself? instead of a bool value?
The key then could be rage-click-timeout (are we also changing the definition for Dead? if so then dead-click-timeout).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The timeout applies to both rage and dead clicks. Yeah we can make an option, since the other PRs haven't merged yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants