fix(grouping): Parameterize error message fingerprint variables#115496
Merged
lobsterkatie merged 3 commits intoMay 15, 2026
Conversation
scttcper
approved these changes
May 15, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In our grouping algorithm, when using component-based grouping, we parameterize both log and error messages, but when using fingerprint-based grouping, we only parameterize log messages, an inadvertent difference in behavior.
This PR fixes that by extending parameterization to also include the two error message fingerprint variables,
{{ value }}and{{ error.value }}. It also introduces two new variables,{{ raw_value }}and{{ error.raw_value }}, as analogs to the{{ raw_message }}variable, so that people can opt out of the parameterization if they choose to.