feat(issues): Add hex parameterization experiment #93970
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our existing hex parameterization supports hex values of any length however they must begin with either
0x
or0X
. We frequently see hex values in messages which do not have this prefix (ex: trace ids or span ids).This adds support for hex values which do not have the
0x
prefix. To ensure it does not over-parameterize the following requirements:We're replacing the
hex
pattern in place in the experiment so that when this is rolled out it doesn't trigger a rehash.The addition of
EXPERIMENT_PARAMETERIZATION_REGEXES_MAP
and other parameters will all be removed once the rollout of this is completed.