Skip to content

LogRocket

LogRocket reconstructs recorded browser sessions so you can see what someone did around an error and inspect the browser requests and logs that were captured.

Visit LogRocket

What can a replay tell you about a failed save?

Open a recorded session from the Errors view and look at the moment the page stopped responding. The replay reconstructs the page and actions such as clicks. Compare that moment with any recorded browser error, console entry or request status. The recorded request shows the browser side of the failure. Use your server logs or traces to see what happened inside the server.

Add LogRocket to the browser code using your LogRocket app ID. Its browser SDK can report uncaught JavaScript errors. If your app catches an error and you still want it in the Errors view, report it explicitly. Source maps connect shortened build output back to readable source code when you supply the right files.

Which parts of a recording need privacy controls?

Treat the page, request details and console messages as separate places where private data can appear. Mask or exclude the affected page elements. Configure separate rules for request and response URLs, headers and bodies. Keep private values out of console messages or disable their capture.

Review these controls before enabling real sessions. A masked email field can still appear in a recorded request or another part of the page. Limit access to stored recordings and check the recording settings for each project.

How can you check one failed save without customer data?

Use a private disposable demo with a fake Save Preview button and an endpoint that returns a fixed test failure. Before opening it, confirm the app has only fictional data, any live services are disabled or replaced with test services, and the recorder points to a separate test project. If you cannot verify these, sketch the expected replay and request on paper.

  1. Give the demo one known failure
    Use a fictional marker such as sample-47@example.invalid in a demo field. Click Save Preview once. Have the demo show a simple failure message and send no email or write to any database.
  2. Check the session and its data
    Find the test session and compare the click with the failed request. Look for the marker in the replay, request and response details, and console. If it appears, change the capture rules in the demo and try again before enabling real traffic.

What is counted and when does recording stop?

LogRocket lists prices by captured sessions. On November 12, 2026 the public price list showed Free with 1,000 sessions per month and Core with 10,000 at about US$83 per month billed annually. Check the plan's own quota period and replay retention in Settings before using those figures to budget.

Without paid overages, new recordings stop at the applicable quota until it resets. Where overages are enabled, extra captured sessions are charged up to the overage limit you set.

What evidence can you take out of LogRocket?

If your organization allows downloads, the player can export an MP4 clip of up to five minutes. The separate Streaming Data Export add-on sends selected session data to a configured destination after it is enabled. That stream does not backfill old sessions or include request and response bodies.