feat(search): Add recommended_v2 sort using the Postgres-data sort framework#117227
Merged
Conversation
…amework Register a recommended_v2 sort built on the Postgres-data sort framework. It keeps the Snuba recommended score (recency/spike/severity/user impact/event volume) as the base and adds additive boosts for signals the Snuba path cannot see: assignment affinity for the viewer (individual assignment outranks team assignment), the group's Seer fixability score, and Seer agent progress (the furthest issue.agent stage reached, root cause < plan < code changes < PR created). Boost weights are tunable via options. On candidate overflow the sort falls back to the chunked Snuba recommended path. Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Backend
…for v2 weights Co-Authored-By: Claude <noreply@anthropic.com>
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 6471464. Configure here.
scttcper
reviewed
Jun 10, 2026
Seer stages reached before the group's latest SET_REGRESSION activity no longer count toward the recommended_v2 agent boost -- a regression means that fix evidently didn't hold, so stale milestones shouldn't over-rank the issue. Co-Authored-By: Claude <noreply@anthropic.com>
scttcper
approved these changes
Jun 11, 2026
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
2 participants
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.
Adds a
recommended_v2issue sort built on the Postgres-data sort framework (#116896). It keeps the Snubarecommendedaggregation (recency / spike / severity / user impact / event volume) as the base score and layers on additive boosts for signals that live outside ClickHouse:GroupAssignee; anonymous/absent viewers get no boost.Group.seer_fixability_score([0, 1], null scored as 0 —exclude_null_postgres=Falseso unscored groups aren't dropped).issue.agentstage reached per group (root cause < plan < code changes < PR created), resolved fromActivityrecords and normalized to [0, 1].Each boost is
weight * signalwith weights registered as options (snuba.search.recommended.*) so they can be tuned without a deploy, matching how the existing recommended weights work.These signals are an initial test of recommended_v2, more signals will be added and some of these might be taken away.
The sort key is also mapped to the
recommendedaggregation insort_strategies, so when there are too many candidates to score in memory the framework's overflow fallback degrades to the existing chunked Snuba recommended path rather thandate.The sort only activates when explicitly requested via
?sort=recommended_v2, so it's inherently opt-in; this is to prevent anyone using the existed v1 implementation from being affected while we test it