-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
No Console Logs Recorded in the Session Replay #12244
Comments
Hey, we have tests specifically ensuring that this works 🤔 do you have a link to a replay where this happens? Could you try with |
@mydea do we have any size limits on console logs? The log message seems to be quite big. For the error, it looks like it's an uncaught rejection which is capture as an exception to Sentry. We do not display these in the Console tab of Replay unless it was explicitly called with |
Do you mean it doesn't record console.log() but only console.error()? |
We truncate logs when we add them as breadcrumbs to replay - we have specifically a test for this 😅 https://github.com/getsentry/sentry-javascript/blob/develop/dev-packages/browser-integration-tests/suites/replay/captureConsoleLog/test.ts#L59 |
Noticed this while looking into #12244, console should be instrumented just fine in the CDN bundle.
@Hugo-Dz no, we capture both, I was more remarking that the Error message you see in the console is not called with Can you give us a repro for this? Or a publicly accessible URL where we can debug? |
@billyvg For some reasons, logs now shows up in my Replays, not sure why it was not the case before 🤔 You can close this :) |
If somebody encounters this again, please re-open the issue! |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
8.4.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
Expected Result
console.log() statements should be visible in the session replay.
Actual Result
No console.log() statements are visible, although errors are correctly reported.
The text was updated successfully, but these errors were encountered: