-
Notifications
You must be signed in to change notification settings - Fork 177
RequestFetcher doesn't return request #818
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
I started looking into this, we might need to cache the request somewhere early in the live cycle. We do the same in our Laravel SDK, so I think this should work in Symfony as well. |
Why caching? Wouldn't be enough to trigger that earlier, i.e. on |
Because we need the data when an error happens (the easy part) and on transaction finish, which happens on |
Hey, just wondering how it was working before, cause I have a feeling I have the same issue, which for some reason appears only in prod environment and only on some of the endpoints. Did it appear on 5.0 release? |
I have a PR opened that aims to resolve this: #879. |
How do you use Sentry?
Self-hosted / on-premises
SDK version
4.8.0
Steps to reproduce
Make any request with body and you won't see body or method in sentry.
The problem is in
RequestFetcher
which relies on getting request fromRequestStack
. The problem here is that theRequestIntegration
which usesRequestFetcher
to get request runs onkernel.terminate
. By this time, theRequestStack
is empty because the handle method of theHttpKernel
pops that request from the stack and terminate is called after handle.Expected result
Data from request will be logged in sentry
Actual result
No data from request are logged
The text was updated successfully, but these errors were encountered: