Skip to content

Conversation

@Zylphrex
Copy link
Member

@Zylphrex Zylphrex commented Nov 1, 2021

Currently, the rollout strategy requires specifying projects one by one because
we were targeting specific projects during the initial rollout. As the rollout
happens for more projects, we want to be able to roll it out for a percentage of
projects at a time.

Currently, the rollout strategy requires specifying projects one by one because
we were targeting specific projects during the initial rollout. As the rollout
happens for more projects, we want to be able to roll it out for a percentage of
projects at a time.
@Zylphrex Zylphrex requested a review from a team November 1, 2021 17:09
@Zylphrex Zylphrex merged commit c6b7c6e into master Nov 1, 2021
@Zylphrex Zylphrex deleted the feat/add-rollout-percentage-option-for-suspect-spans branch November 1, 2021 17:45
# This is to enable the ingestion of suspect spans by project ids.
register("performance.suspect-spans-ingestion-projects", default={})
# This is to enable the ingestion of suspect spans by project groups.
register("performance.suspect-spans-ingestion.rollout-rate", default=0)
Copy link
Member

Choose a reason for hiding this comment

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

@Zylphrex would using FLAG_PRIORITIZE_DISK here be preferred?

Copy link
Member Author

Choose a reason for hiding this comment

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

Hm... I'll double check 👍

Zylphrex added a commit to getsentry/snuba that referenced this pull request Nov 3, 2021
Previously, suspect span ingestion can only be enabled on a per project basis.
This change allows us to enable it for a percentage of projects at a time. See
getsentry/getsentry#6531 and getsentry/sentry#29692  for the sentry PRs.
@github-actions github-actions bot locked and limited conversation to collaborators Nov 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants