Skip to content

Analytics: add feature flag to skip tracking 404s #9131

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

Merged
merged 3 commits into from
Apr 21, 2022

Conversation

stsewd
Copy link
Member

@stsewd stsewd commented Apr 21, 2022

No description provided.

@stsewd stsewd requested a review from a team as a code owner April 21, 2022 17:54
Copy link
Member

@ericholscher ericholscher left a comment

Choose a reason for hiding this comment

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

We want to be able to opt certain projects in to this feature, so I think we want to invert the logic here. On .org we'll basically just keep it off for everyone, and .com we'll past_default_true and future_default_true it.

If it's inverted, I don't think we have a way to turn it on for select projects on .org, if needed.

@ericholscher ericholscher added the PR: hotfix Pull request applied as hotfix to release label Apr 21, 2022
@ericholscher ericholscher merged commit 7909b9f into main Apr 21, 2022
@ericholscher ericholscher deleted the ff-disable-record-404s branch April 21, 2022 20:49
ericholscher pushed a commit that referenced this pull request Apr 21, 2022
* Analytics: add feature flag to skip tracking 404s

* Invert feature flag

* Fix tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: hotfix Pull request applied as hotfix to release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants