Issue
I see errors in Sentry either grouped incorrectly under the same issue or the same event separated into different issues even though they seem related.
Applies To
- All SaaS Users
- Error Monitoring
- Grouping / Fingerprinting
Symptoms
- Different errors grouped together despite having different attributes like titles
- Related errors separated into different issues
Resolution
- Events with the same fingerprint are grouped into the same issue. By default, the grouping algorithm prioritizes:
- Stack trace first
- Exception next
- Message last
- To see the specific rule setting the fingerprint for an issue:
- Scroll to the bottom of the issue details page
- Click on "Show Details" next to "Event Grouping Information".
- Default grouping behaviour cannot be changed, however, you can override it using these options:
-
SDK Configuration:
- Take a look at the SDK Fingerprinting documentation page and the documentation specific to your SDK
-
Project Settings:
- Navigate to Sentry settings.
- Select your project.
- Go to the "Issue Grouping" section.
- Define custom Fingerprint Rules based on your specific requirements. Read the fingerprint rules and Issue Grouping documentation to learn more.
-
SDK Configuration: