ref(grouping): Change designations for enhancement actions and rules #87655
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 current grouping enhancements code, we designate actions (and thereby rules containing said actions) as "modifiers" and/or "updaters," and we provide the ability to split a rule which is both into a modifier version and an updater version. There are two problems with that: 1) Updating and modifying are effectively synonymous concepts, and so it's not at all clear what it means to be one or the other. 2) We actually shouldn't even have this code anymore, because it's a relic of both the pre-rust-enhancements era and the hierarchical grouping era, and is no longer used.
Rather than remove the code, though, we can actually repurpose it. During ingest, we run the stacktrace through the rules twice, once to assign
in_appandcategoryvalues to frames, and once to setcontributesvalues on both the frames and the overall stacktrace. Being able to split a given set of rules into ones useful for the first task and ones useful for the second task would actually be helpful, because at each stage it would allow us to avoid checking rules we know won't apply. It also would solve the problem of "marked in-app by rule x" hints clobbering "ignored by rule x" hints (and vice versa) in cases where a single rule has both effects.This PR therefore changes the existing designations from
is_modifierandis_updatertois_classifierandsets_contributes(for actions) andhas_classifier_actionsandhas_contributes_actions(for rules). Further changes to use this information will come in follow-up PRs.Note to reviewers: I super don't love the non-parallel naming with
is_classifierandsets_contributes, but I struggled to find anything with parallel structure that wasn't horribly ungrammatical. Definitely open to ideas here.