You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our existing hex parameterization supports hex values of any length
however they must begin with either `0x` or `0X`. 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:
- Must be exactly 4 or 8 bytes (8 or 16 characters)
- Must contain both a number and a letter
- Must use lowercase letters (anecdotally I've never seen examples where
uppercase would be beneficial)
The addition of `EXPERIMENT_PARAMETERIZATION_REGEXES_MAP` and other
parameters will all be removed once the rollout of this is completed.
0 commit comments