Configured Sentry for our Express app but we are getting a new issue created for the same exception but for different user ids.
See:
How do we group issues by Error Class, Filename, and Line Number? The error message should be ignored. This is the way that BugSnag has their reporting setup.
@BioJoseph it’s a hiccup on our end. It’s fixed and pending release in v5, as it’s a breaking change. Should be released within next week or two.
In the meantime, you can configure correct behaviour with this snippet
Sentry.configureScope((scope) => {
scope.setFingerprint(['{{ default }}']);
});
1 Like