getsentry / getsentry/sentry

[grouping info] Include Seer as grouping reason

Open
#94,805 0 comments 0 reactions 0 assignees View on GitHub
Improvement
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

When Seer is used to assign an event to an existing group, we give no indication of that in the grouping info, but we should.

UPDATE: We do now show it in the merged issues tab, which is a good start, but leaving this open to track actually adding it to grouping info.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how grouping information is generated when Seer assigns an event to an existing group, then compare that path with the merged issues tab where Seer is already shown. Done means grouping info explicitly indicates Seer as the grouping reason for those events.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.