Skip to main content

Command Palette

Search for a command to run...

Session replay scoping that keeps production privacy and signal

Updated
1 min readView as Markdown
Session replay scoping that keeps production privacy and signal

Session replay is useful in production only when you decide what gets recorded, how often, and what never leaves the browser. If you turn it on at 100% with masking relaxed "just for a week," you buy noise and privacy risk. If you leave defaults alone and pick sample rates from real traffic, you get the sessions that explain bugs — without shipping PII.

This post is about scoping: replaysSessionSampleRate, replaysOnErrorSampleRate, privacy masking defaults, and error-first capture. It is not a crash triage walkthrough, not LLM tracing, and not release health.


This is an excerpt. Read the full post at otf-kit.dev/blog/session-replay-scoping-production — full-stack kits your AI coding agent can actually ship to production. Browse the kits →

More from this blog