-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Closed
Labels
Package: nodeIssues related to the Sentry Node SDKIssues related to the Sentry Node SDK
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
7.51.2
Framework Version
No response
Link to Sentry event
https://algolia-site-search-crawler.sentry.io/issues/4155211403/?project=1260143
SDK Setup
Sentry.init({
dsn: process.env.SENTRY_DSN,
release: `${version}@${commit}`,
environment: process.env.CLUSTER_NAME || process.env.NODE_ENV,
serverName: name,
maxBreadcrumbs: 10,
beforeSend: (event, hint) => {
const exception = hint?.originalException;
if (exception) {
if (exception instanceof RabbitMQAckMessageOnOldChannelError) {
// eslint-disable-next-line no-param-reassign
event.fingerprint = ['RabbitMQAckMessageOnOldChannelError'];
}
}
return event;
},
});Steps to Reproduce
Run our process as before
Expected Result
No unhandled error coming from the Undici integration
Actual Result
Those unhandled errors started to make our processes crash, immediately after we updated to Sentry v7.50, which enables the Undici integration by default (#7967):

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Package: nodeIssues related to the Sentry Node SDKIssues related to the Sentry Node SDK
Fields
Give feedbackNo fields configured for issues without a type.