-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
[Epic] Replay: HTTP Request/Response in Network tab #45525
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
Routing to @getsentry/replay for triage, due by Thursday, March 9th at 1:32 pm (sfo). ⏲️ |
We considered adding req/resp to Sentry breadcrumbs in this PR: Finally decided against it for a few reasons: We keep around by default 100 crumbs. This means changes are high that we'll go over the event size limit and the event will be dropped instead. Also that would require work on the event detail and transaction breadcrumb component to render these properly. Truncation was considered to keep the size within certain limits but as we did that with |
Enabled the feature to all EA customers. Let folks know in: getsentry/sentry-javascript#7103 (comment) |
Rolled out to 100% of customers. Docs: https://docs.sentry.io/platforms/javascript/session-replay/configuration/#network-details |
Uh oh!
There was an error while loading. Please reload this page.
This tracks the work required to deliver network request/response on Replay the Network tab.
It's a very common customer request.
JS SDK tracking this: getsentry/sentry-javascript#7103 (several 👍 here).
The text was updated successfully, but these errors were encountered: