Skip to content

Commit

Permalink
feat(Browser): re-added session replay GA doc changes
Browse files Browse the repository at this point in the history
  • Loading branch information
jeff-colucci committed May 14, 2024
1 parent 5d2d6e9 commit e5b2a90
Showing 1 changed file with 1 addition and 19 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,6 @@ import browserErrorsInboxSessionReplay from 'images/browser_screenshot-full_erro

import browserViewConsumptionDetails from 'images/browser_screenshot-crop_view-consumption-details.webp'

<Callout variant="important">
Session replay is in limited preview. This feature will be billable starting May 15, 2024. See [Data consumption](#plan-for-paid-consumption) for details.
</Callout>

Session replay plays back user interactions on your web app and maps other telemetry data to help you understand your user's journeys. Session replay can be used for troubleshooting and improving the end-user experience, such as:

* **Troubleshooting JavaScript errors**: Troubleshoot the cause of an error by seeing what the user was doing when the error occurred. For example, if an end user receives an error while trying to complete an ecommerce transaction, you can use session replay to see which steps they took and what data they entered before the error occurred. This can help you quickly identify and fix the root cause of the problem.
Expand Down Expand Up @@ -394,23 +390,9 @@ Here's an example mutation and variables to create a new browser application wit

## Data consumption [#data-consumption]

### View consumption [#view-consumption]

Before May 15, 2024, while session replay bytes are free, you can view your consumption to help with planning once the bytes become paid:
1. Go to <DoNotTranslate>**Application Settings**</DoNotTranslate>.
2. Scroll down to <DoNotTranslate>**Session replay**</DoNotTranslate>.
3. In the <DoNotTranslate>**Session sample size**</DoNotTranslate> section, click <DoNotTranslate>**View your account's consumption**</DoNotTranslate>.

<img
title="View account consumption on application settings page"
alt="screenshot of application settings page"
src={browserViewConsumptionDetails}
style={{ maxWidth: '50%' }}
/>

### Plan for paid consumption [#plan-for-paid-consumption]

After May 15, 2024, session replay will follow the same consumption pricing as your other browser bytes. The amount of bytes produced depends on the count, length, and user-activity levels of sessions, as well as the complexity of your site's DOM.
Session replay follows the same consumption pricing as your other browser bytes. The amount of bytes produced depends on the count, length, and user-activity levels of sessions, as well as the complexity of your site's DOM.

The most accurate way to project your cost per replay is to enable the feature for a short test period and measure your actual consumption. Alternatively, you can use an average of 5.3 MB per replay as a rough approximation, though keep in mind that your actual cost may vary significantly. A simple formula to project your approximate costs is: `sessions` x `sampling_rate` x `gb_per_replay` x `cost_per_gb`
* Example: `sessions: 1 million` x `sampling_rate: 5%` x `gb_per_replay: 0.0053` x `cost_per_gb: $0.30` = `$79.50 for 50,000 replays`
Expand Down

0 comments on commit e5b2a90

Please sign in to comment.