-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(node): Drop http.server
spans with 404 status by default
#16205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
size-limit report 📦
|
This can be configured via `dropSpansForIncomingRequestStatusCodes` option in `httpIntegration()`.
transport: loggingTransport, | ||
integrations: [ | ||
Sentry.httpIntegration({ | ||
dropSpansForIncomingRequestStatusCodes: [499, /3\d{2}/], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The regex is an interesting API choice. I can kindof see the reason, just wanna suggest other options that might be a bit more intuitive to write and don't require googling what the regex for numbers is, like:
- Providing intervals to drop for ranges like
[from, to]
e.g.[400, 499]
. - Providing strings with
x
as a wildcard e.g."4xx"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I know what you mean. The drop ranges seem fine to me too, I'll adjust it to that instead!
@@ -125,20 +125,3 @@ test('Should send a transaction event with correct status for a generateMetadata | |||
|
|||
expect((await transactionPromise).contexts?.trace?.status).toBe('ok'); | |||
}); | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lforst removed this test as this is no longer sent
This can be configured like this:
It defaults to
[404]
.Closes #16193