Session replay is a reconstruction of what happened in a user’s browser, rebuilt from DOM snapshots and recorded events, so you can watch the sequence that led to an error instead of asking the user to describe it.
The player rebuilds the page from recorded DOM mutations, which is why a replay is small enough to attach to an error and why masking can be applied to individual elements.
Example
import Rollbar from 'rollbar/replay';
const rollbar = new Rollbar({
accessToken: '[POST_CLIENT_ITEM_TOKEN]',
replay: { enabled: true, maskAllInputs: true },
});
What Rollbar does with session replay
Rollbar attaches the replay to the error item, so the recording sits next to the stack trace instead of in a separate tool. Rollbar starts a capture on one of three trigger types: an occurrence at a matching severity level, a navigation to a matching path, or a direct call to Rollbar.triggerDirectReplay(). Each trigger carries its own sampling ratio, pre-duration and post-duration, so you can record every critical error in full and sample warnings at ten percent.
Rollbar masks input values through CSS classes and selectors, blocks whole elements from recording with blockSelector, and masks password inputs by default. Every Rollbar account includes 1,000 replays a month, and the recorder adds roughly 124kb to over-the-wire page load.
Related terms
Sources
- Rollbar Docs, Session Replay: https://docs.rollbar.com/docs/session-replay
