Guide
Session Replay & Profiling
1 min read
Replays show what the user did; profiles show where the CPU went. Both arrive through the standard SDK envelope — no extra endpoints to wire.
Session Replay
Sentry.init({
dsn: '…@jentry.app/<projectId>',
integrations: [Sentry.replayIntegration()],
replaysSessionSampleRate: 0.05, // 5% of sessions
replaysOnErrorSampleRate: 1.0, // always when an error happens
});- The SDK's compressed recordings (zlib/gzip) are decoded on ingest; segments of one session merge into a single replay.
- Replays list per project/org with duration and event counts; the detail page plays the DOM recording.
- Recordings are capped (~20k rrweb events per replay) so a runaway session can't bloat storage.
Profiling
jentry aggregates each profile into per-function self/total time (the Slowest Functions table) and a flame graph — an icicle view of the call tree where each frame's width is its share of samples; click a frame to zoom into its subtree. Profiles link back to their trace.
Privacy note: replays record DOM content. Use the SDK's masking options (maskAllText, blockSelector) for sensitive UIs — masking is enforced client-side by the SDK before anything is sent.
Try jentry free
Hosted error tracking & performance monitoring. Works with your Sentry SDKs — send your first event in minutes.