When there are exceptions in the frontend, it's often helpful to see how the user arrived at the buggy application state, or if the exception impacted the user's experience:
See Error Reporting for more information on how to use LogRocket error reporting.
Alternatively, integrate LogRocket with your existing exception logging tools lets you see the corresponding LogRocket session for every error:
See documentation on our Error Reporting integrations for how to add LogRocket sessions to your crash reports:
Read more about the data that LogRocket collects to help you reproduce frontend bugs.
Updated almost 3 years ago