Repository navigation
No Console Logs Recorded in the Session Replay #12244
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
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
- Implement Sentry as described in the attached screenshots.
- Trigger console.log() statements in the client.
- Check the session replay for recorded console logs.
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.
Activity
mydea commentedon May 28, 2024
Hey,
we have tests specifically ensuring that this works 🤔 do you have a link to a replay where this happens? Could you try with
debug: trueenabled, would be interesting to see where the logs go in terms of timeline.billyvg commentedon May 28, 2024
@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
console.error().Hugo-Dz commentedon May 28, 2024
Do you mean it doesn't record console.log() but only console.error()?
mydea commentedon May 29, 2024
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
test(replay): Remove outdated test constraint (#12270)
billyvg commentedon May 30, 2024
@Hugo-Dz no, we capture both, I was more remarking that the Error message you see in the console is not called with
console.errorand so it's expected that you won't see it in the Replay's Console tab (this is because it's captured as an exception and displayed in Breadcrumbs).Can you give us a repro for this? Or a publicly accessible URL where we can debug?
Hugo-Dz commentedon May 30, 2024
@billyvg For some reasons, logs now shows up in my Replays, not sure why it was not the case before 🤔
You can close this :)
mydea commentedon May 31, 2024
If somebody encounters this again, please re-open the issue!