Error reporting issues

Errors are not appearing

If errors you expect to see on your dashboard are missing, check the following.

• If you're using Angular or another similar framework, make sure uncaught exceptions aren't being swallowed by ErrorHandler or another similar handler. The LogRocket SDK captures and reports on uncaught exceptions by wrapping your application code with a try/catch. If something else intercepts uncaught exceptions without re-throwing them, LogRocket won't be able to report them. The default implementation of ErrorHandler prints error messages to the console without re-throwing them. Errors will be reported correctly if you write a custom exception handler that re-throws caught exceptions or passes them directly to LogRocket.captureException().

• If you're using Ember, make sure to send data from Ember.onerror into LogRocket.captureException().

If you want aggregated data about messages logged with console.error() to be surfaced in LogRocket error reporting, pass the console.shouldAggregateConsoleErrors option when calling LogRocket.init().

LogRocket is showing up as the source of my errors

The LogRocket Web SDKs work by intercepting built-in browser APIs that power things like network requests and logging (including console.log and XMLHTTPRequest). Due to that, our SDK will appear at the top of the stacktrace/initiator for those in your browser’s developer tools. When we log to the console in the course of recording a session (for instance, when there is a problem recording), those logs are prefixed with “LogRocket”.

You can add the LogRocket script to your browser's Ignore List (see Chrome documentation here), which will cause the browser to ignore the LogRocket SDK when showing stack traces.