Skip to main content

Why Are My Events Grouped or Separated Incorrectly in Sentry?

Updated over a month ago

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 are separated into different issues

Resolution

Sentry uses the event's "fingerprint" to group events into issues. Events with the same fingerprint are grouped into the same issue. By default, the grouping algorithm prioritises:

  • Stack trace first

  • Exception next

  • Message last

You can see the information used to group each issue by scrolling to the bottom of the issue details page and clicking on "Show Details" next to "Event Grouping Information":

The default grouping behaviour can be customised using one of the following options

The full documentation on issue grouping is available here.

Did this answer your question?