feat(seer grouping): Add call to Seer to optimized grouping flow in ingest #75266
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.
There are currently two paths ingest can follow when saving an event: the existing
_save_aggregate
(which runs unnecessary calculations when a project is in a grouping config transition) and the newer_save_aggregate_new
(which only does extra calculations when necessary). Until now, Seer grouping had only been integrated into the first path, meaning we had to turn off the second path entirely. This adds the Seer logic to the new path, so we don't have to choose between the features.Note: The tests look like they've changed more than they actually have. In reality, all that's happened is that the body of each test has been parameterized and wrapped in the following code, which forces it to run through both paths mentioned above: