Running LogRocket?

LogRocket replays misbehaving or leaking data? We sort it out.

LogRocket shines once it is tuned to your app, but the defaults happily record credit card inputs, merge every SPA route into one session, and silently drop network bodies over the size limit. We tighten the sanitization, fix the Redux and router integrations, and leave you with replays you can actually hand to support.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

logrocket-init.log

still broken

What it is

LogRocket at a glance

LogRocket is a session replay and front-end monitoring product aimed at web application teams. It records user sessions as pixel-perfect video, captures console logs, network traffic, Redux actions, and JavaScript errors, then ties them back to the user and the release so you can see exactly what a person saw when a bug happened.

The company was founded in 2016 and is headquartered in Boston. Pricing is based on retained sessions per month, with a free developer tier and separate add-ons for AI analytics and heatmaps. Integrations exist for most popular SPAs, with first-party plugins for React, Redux, Vue, Angular, Next.js and NgRx.

Type
Session replay and front-end observability
First released
2016
License
Proprietary SaaS, per-session pricing
Maintained by
LogRocket, Inc.
Typically used for
Reproducing frontend bugs, product analytics on web apps, support triage, performance review

The honest version

LogRocket pros and cons

No technology is all upside. This is where LogRocket earns its place and where it tends to cause trouble.

Where LogRocket is strong

  • Replays that feel like sitting next to the userThe video is reconstructed from the DOM, so you get pixel accuracy without shipping actual video bytes, which keeps the bandwidth cost sensible.
  • Redux and NgRx action streamsYou can scrub through the session and watch state transitions alongside the UI, which cuts the time to reproduce a nasty state bug to minutes.
  • Error and network capture in one placeA JavaScript exception, the XHR that triggered it, and the click that led to it all sit in the same timeline, so the hop between tools goes away.
  • Decent framework pluginsThe React, Vue and Angular integrations instrument component names, props and router events without you writing wrappers.
  • Feature flag and release taggingSessions can be filtered by release, experiment or custom user traits, which makes regression triage after a deploy tolerable.

Where LogRocket bites

  • Default sanitization misses almost everythingOut of the box LogRocket records credit card fields, password confirmations, and any custom input that is not a stock HTML password. You have to write explicit rules.
  • Per-session pricing is punishing at scaleA high-traffic consumer site burns through a plan quickly, and the step changes between tiers are steep enough to force sampling decisions.
  • SPA route tracking needs manual helpClient-side navigation does not always fire a session boundary, so a single recording can cover three unrelated flows unless you call the router hook yourself.
  • Network body limits bite silentlyResponse bodies over the configured size are dropped without a warning in the UI, which is how a bug report arrives with an empty network panel.
  • CSP and ad blockers are a running battleStrict Content-Security-Policy headers, Safari ITP and tracker blockers each have their own ways of breaking the SDK, and the symptoms look like a quiet session gap.
  • Data residency is limitedEU-based replay storage exists as a premium add-on, so a straight US tenancy can be awkward for GDPR-sensitive teams.

Sound familiar?

Common LogRocket problems we fix

The LogRocket problems that bring people to us, and what you have once each one is fixed.

LogRocket: session URL could not be generated

Sessions are not starting at all

init was called from the wrong entry point, a CSP header blocked the CDN, or identify fired before init so the first session never anchored to a user.

Sessions anchored to real users

Network request body exceeded 1MB

Network tab is empty where it matters

The response that caused the bug was over the capture limit, got truncated, and the replay now shows a 200 with no body. We raise the cap, redact selectively and keep the payload that actually proves the issue.

Bodies captured without leaking PII

ignoring sanitization rule, selector did not match

PII is leaking into recordings

A redaction rule pointed at a class that was renamed, or a custom input that is neither type=password nor marked with data-private. We audit the DOM and rewrite the rules.

Sensitive fields redacted at the browser

SPA route change detected, stitching into existing session

One session covers three unrelated flows

A client-side router that does not emit a hook LogRocket listens for, so checkout, settings and login all end up as one blob of a recording.

Sessions split per logical flow

CSP violation: script-src blocked cdn.logrocket.io

Strict CSP is blocking the SDK

A security header tightened last quarter now blocks the LogRocket runtime, ad scripts and everything else that was not on the allowlist.

CSP tuned, SDK reinstated

Session quota exceeded for the current billing period

The plan runs out mid-month

An ingest rule that records every visitor including bots and scrapers, so the quota is consumed by traffic you did not want replays of in the first place.

Sampling that keeps the signal

redux middleware: action payload dropped

Redux actions go missing from the timeline

A reducer payload that is not JSON-serializable, a Map, a Date, or a class instance. The middleware drops it silently and the state transition looks empty.

Actions captured, payloads clean

What we do

LogRocket help, from setup to tuning

Call us for a single leaky replay, or hand us the LogRocket account end to end.

Rescue
Replays missing, PII leaking, or the quota blown halfway through the month. We stabilise the setup and explain the holes.
Sanitization audit
A full pass of your DOM against the redaction rules, with selectors that survive a rename and a test harness that catches regressions.
SPA integration
Router hooks, Redux middleware, release tagging and feature flag wiring so sessions line up with the thing you actually shipped.
Quota and sampling
Bot filtering, session conditions and plan sizing worked against your traffic so the bill does not jump the week a campaign lands.
Managed Tech
We watch the ingest health, keep the SDK up to date with your framework, review new redaction rules before a deploy, and sit on the other end of the phone when a replay goes missing.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running LogRocket alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

LogRocket questions

Something else? Call+1 737 727 7327

Why are my LogRocket sessions not recording?

Most of the time it is one of three issues: init is called from a file that never runs on first load, a Content-Security-Policy header blocks the CDN domain, or identify fires before init and the first session never anchors to a user. The dashboard tells you how many sessions started per release, so comparing before and after a deploy usually pinpoints the regression.

How do I stop LogRocket recording credit cards and passwords?

You cannot rely on the defaults. Mark the containing elements with data-private, add explicit input sanitization rules in the SDK config, and verify the result by watching a test session back. For PCI scope, the browser needs to never see the full PAN, which usually means an iframe from your payment processor rather than a LogRocket rule.

Why does one LogRocket session cover three different pages?

A single page application without a router hook looks like one long session to the SDK. Call LogRocket.track on route changes, or wire the router integration for React Router, Vue Router or Angular. After that the session timeline splits properly and support can jump straight to the relevant flow.

How much data does LogRocket add to my pages?

The runtime is roughly 60KB gzipped and the session stream is throttled, so the bandwidth cost is modest for most apps. Heavy canvas or video content can bump it, and the console plugin is the usual suspect when a slow page gets slower after enabling replay.

Can we host LogRocket data in the EU?

There is a separate EU tenancy that keeps replays on European infrastructure, but it is an upgrade rather than a default. If you are already on the US ingest, moving across means a new project, new SDK config and a cutover window.

How much does LogRocket help cost?

The estimate is free. Tell us what the account is doing, where the replays are falling short, and we come back with a figure before any work begins.

Free estimate

LogRocket giving you trouble?

Share the account, the SDK version and which flows are not replaying. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.