I’m working on a sentry sdk for C++. Sentry is too eagerly grouping the events that I generate - at least more eagerly than I expect, as sentry groups events with different stacktraces. I don’t have a stacktrace element directly in the event, only as part of the threads interface element. I’ve marked the crashing thread with “crashed”: true, so it seems reasonable that sentry should pick it up from there and use it for grouping.
According to the grouping-by-stacktrace documentation “When Sentry detects a stacktrace in the event data (either directly or as part of an exception) the grouping effectively is based entirely on the stacktrace.“ If this documentation is accurate it explains the behaviour I’m seeing, since my stacktrace elements are parts of thread elements.
My question is whether the documentation is accurate, and if it is, why doesn’t sentry use the stacktrace of the thread that is marked as crashed, if it is there?