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
feat(replay): Capture fetch body size for replay events #7524
Conversation
size-limit report 📦
|
Tested this on my local Sentry and it works - though I do want to note that the sizes are slightly off from the browser which shows the size over the network (which I assume is smaller due to compression). Thoughts on the best way to inform users on the UI here since we display the "resource size" that is on the tooltip vs "transferred over the network". |
It may also differ because I guess the network tab includes header etc. data into the size, maybe? But even if not it could def. be slightly different, hard to say how exactly that is calculated..! |
9bcd880
to
45b1660
Compare
45b1660
to
a34ab79
Compare
This adjusts the replay request body capturing to capture the fetch body size if no Content-Length header is present.