RFC: Sentry Issues with missing stack traces

[lforst]

You might have noticed in Sentry, when browsing through your issues, that some of them do not have a stack trace attached. A common issue type where this happens is, for example, on TypeError: Failed to fetch errors.

You've probably seen it before:

We generally do not like issues without stack traces because they mess up Sentry's fingerprinting/grouping algorithm: All the issues that share a name and do not have a stack trace are now grouped into the same issue - even when the errors might come from completely different places in your application! It sucks trying to fix these errors when you don't know where they happen. Additionally, it's impossible to know which ones are the most important because all of them are grouped into one, so you can't see the event count of individual errors!

We want to fix this.

As part of our initiative to improve the workflow and grouping on Sentry (https://github.com/getsentry/sentry-javascript/milestone/17, getsentry/sentry#34327) we want to resolve this issue once and for all (or at least improve it step by step).

Currently, we're investigating what class of errors doesn't have stack traces.
We suspect that it is mostly related to fetch in some way, but we're not sure if this covers all instances.

Anybody can help us to solve this issue!

As we're trying to figure out what causes errors without stack trace, anybody can help us investigate by sharing experiences surrounding the issue:

• Have you ever encountered errors in Sentry without a stack trace?
• Were you able to resolve errors without stack trace when you encountered them?
• Have you noticed a pattern for errors without stack trace?

Next steps

• Identify the problem
• Reproduce the issue consistently
• Brainstorm how to provide a stack trace for errors without