|
1 | 1 | --- |
2 | 2 | title: "Session Replay" |
3 | 3 | sidebar_order: 60 |
4 | | -description: "Learn about Sentry's Session Replay, which provides video-like reproductions of user interactions on a site or web app." |
| 4 | +description: "Use Session Replay to get video-like reproductions of user interactions to improve your website or app experience. Learn about Sentry’s Session Replay here." |
5 | 5 | --- |
6 | 6 |
|
7 | 7 | <Include name="feature-stage-beta-session-replay.mdx" /> |
8 | 8 |
|
9 | | -Session Replay shows you a video-like reproduction of your user sessions so you can see what happened before, during, and after an error or performance issue occurred. Gain deeper debugging context into issues so that you can reproduce and resolve problems faster without the guesswork. As you play back each session, you can see every user interaction in relation to network requests, DOM events, and console messages. It’s effectively like having [DevTools](https://developer.chrome.com/docs/devtools/overview/) active in your production user sessions. |
| 9 | +Session Replay allows you to see video-like reproductions of user sessions which can help you understand what happened before, during, and after an error or performance issue occurred. You'll be able to gain deeper debugging context into issues so that you can reproduce and resolve problems faster without the guesswork. As you play back each session, you'll be able to see every user interaction in relation to network requests, DOM events, and console messages. It’s effectively like having [DevTools](https://developer.chrome.com/docs/devtools/overview/) active in your production user sessions. |
10 | 10 |
|
11 | | -Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/performance/transaction-summary/) page. For [backend error replays](/product/session-replay/getting-started#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, breadcrumbs, and errors. |
| 11 | +Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see session replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/performance/transaction-summary/) page. For [backend error replays](/product/session-replay/getting-started#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, [breadcrumbs](https://docs.sentry.io/product/issues/issue-details/breadcrumbs/), and errors. |
12 | 12 |
|
13 | 13 |  |
14 | 14 |
|
15 | | -## What is a Replay? |
| 15 | +## What Is a Session Replay? |
16 | 16 |
|
17 | | -A replay is **not** a video recording. It’s a video-like reproduction of a user session, built using the [rrweb recording library](https://www.rrweb.io/). Replays are created from snapshots of your web application’s DOM state (the browser’s in-memory representation of HTML). When each snapshot is played back, you will see a video-like recording of what the user did throughout their entire session. The user session includes any pageloads, refreshes, and navigations that happened while the user was on your site. |
| 17 | +A session replay is **not** a video recording. It’s a video-like reproduction of a user session, built using the [rrweb recording library](https://www.rrweb.io/). Replays are created from snapshots of your web application’s DOM state (the browser’s in-memory representation of HTML). When each snapshot is played back, you will see a video-like recording of what the user did throughout their entire session. The user session includes any pageloads, refreshes, and navigations that happened while the user was on your site. |
18 | 18 |
|
19 | 19 |  |
20 | 20 |
|
21 | | -The start of a replay recording can be triggered by: |
| 21 | +The start of a session replay recording can be triggered by: |
22 | 22 |
|
23 | | -- A user session being part of a sampling rate, as controlled by [replaysSessionSampleRate](/platforms/javascript/session-replay/#sampling). When a user loads a page, a decision is made whether to sample it or not. |
24 | | -- An error occurring during a session that’s not being recorded. The session is then recorded based on [replaysOnErrorSampleRate](/platforms/javascript/session-replay/#sampling) |
25 | | -- Manually calling the [replay.start()](/platforms/javascript/session-replay/understanding-sessions/#manually-starting-replay) method |
| 23 | +- A user session being part of a sampling rate, as controlled by [`replaysSessionSampleRate`](/platforms/javascript/session-replay/#sampling). (When a user loads a page, a decision is made whether to sample it or not.) |
| 24 | +- An error occurring during a session that’s not being recorded. The session is then recorded based on [`replaysOnErrorSampleRate`](/platforms/javascript/session-replay/#sampling). |
| 25 | +- Manually calling the [`replay.start()`](/platforms/javascript/session-replay/understanding-sessions/#manually-starting-replay) method. |
26 | 26 |
|
27 | | -The end of a replay recording can be triggered by: |
| 27 | +The end of a session replay recording can be triggered by: |
28 | 28 |
|
29 | | -- User inactivity within the tab/page that’s being recorded. (If a user doesn’t click or navigate around the site for more than 15 minutes. Mouse scrolls, mouse movements, and keyboard events don’t currently qualify as activity.) |
30 | | -- A recording reaching the maximum replay duration limit (currently 60 minutes) |
31 | | -- Manually calling the [replay.stop()](/platforms/javascript/session-replay/understanding-sessions/#manually-stopping-replay) method |
| 29 | +- User inactivity within the tab or page that’s being recorded. (It's considered inactivity when a user doesn’t click or navigate around the site for more than 15 minutes. Mouse scrolls, mouse movements, and keyboard events don’t currently qualify as activity.) |
| 30 | +- A recording reaching the maximum replay duration limit. (Currently, this is 60 minutes.) |
| 31 | +- Manually calling the [`replay.stop()`](/platforms/javascript/session-replay/understanding-sessions/#manually-stopping-replay) method. |
32 | 32 |
|
33 | 33 | <Note> |
34 | 34 |
|
35 | 35 | Unlike [sessions](/product/releases/health/#session) on the **Releases** page, user sessions in Session Replay can span multiple page loads. |
36 | 36 |
|
37 | 37 | </Note> |
38 | 38 |
|
39 | | -## Learn More |
| 39 | +## Learn More About Session Replay |
40 | 40 |
|
41 | 41 | <PageGrid /> |
0 commit comments