Consider all stack traces for grouping

[kerenkhatiwada]

Problem Statement

At the moment it seems Sentry groups using only one stack trace. This is an issue when there are two stack traces for an issue that are completely different.

Solution Brainstorm

Consider all stack traces for grouping

Product Area

Issues

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[lobsterkatie]

@kerenkhatiwada, can you please share some links to events which show this behavior? And when you say "multiple stacktraces," do you mean events with error groups or chained errors, or something else?

[kerenkhatiwada]

Here is an event where we were able to reproduce it. This occurs for javascript error.cause issues. However, AggregateErrors are grouped by all stack traces.