-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
beforeBreadcrumb can no longer access original Request object in v8 #12132
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
Comments
Hey, thanks for writing in - that is indeed not on purpose, we'll add this back, sorry about the inconvenience! |
@mydea Thanks for looking into this. Just to double-check this desired behavior is expected for both |
Yeah, you are right! While looking into this some more I noticed that we have some general issues there, mainly that breadcrumbs were (incorrectly) tied to spans, meaning that if performance was disabled we would not get proper breadcrumbs. I opened a PR to fix this: #12137 and ensure this is consistent, including passing the request/response as hints! |
This may be related: I had to set |
Yeah, this is also fixed in my PR - should not be necessary! |
This PR ensures that (node) fetch and http requests generate breadcrumbs correctly, even if tracing is disabled. It also adds tests for this, and ensures we pass the request/response to the hint correctly. Fixes #12132
Uh oh!
There was an error while loading. Please reload this page.
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.2.1
Framework Version
No response
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
Expected Result
The
beforeBreadcrumb
handler should receive the original fetch Request object as a hint parameter. This is used to extract the fetch request headers and apply this information to enrich the breadcrumb.Actual Result
The
beforeBreadcrumb
handler does not receive the original fetch Request object anymore since Sentry v8The text was updated successfully, but these errors were encountered: