You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It tries to get the status of the exception by calling exception.status. However, if we follow the nestjs docs and throw exceptions, the status should be read with exception.getStatus().
Expected Result
Http errors where status is >=400 and <500 should not be reported to sentry
Actual Result
Http errors where status is >=400 and <500 are reported to sentry
The text was updated successfully, but these errors were encountered:
Hey, this feature was only recently introduced and was not yet part of the 8.13.0 SDK release. We just released 8.14.0, which now includes the filtering. So updating to 8.14.0 should fix your issue.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
8.13.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup/Reproduction Example
No response
Steps to Reproduce
The issue is with this line:
sentry-javascript/packages/node/src/integrations/tracing/nest.ts
Line 103 in 13ff71f
It tries to get the status of the exception by calling
exception.status
. However, if we follow the nestjs docs and throw exceptions, the status should be read withexception.getStatus()
.Expected Result
Http errors where status is >=400 and <500 should not be reported to sentry
Actual Result
Http errors where status is >=400 and <500 are reported to sentry
The text was updated successfully, but these errors were encountered: