Maximum Session Replay Duration Configuration

[jsfeb26]

Problem Statement

I want to capture 60 seconds before and 60 seconds after an error occurs. Our primary focus is on understanding how users encounter errors, so we don't need to record an entire 60 minutes after the error occurs

Currently, we are receiving really long session replays, whereas our main interest lies in the moments immediately preceding the error, along with a brief period thereafter. The majority of the replay consists of activities performed by users after the error, which is not important to us.

Solution Brainstorm

A simple solution would be a maxReplayDuration similar to the minReplayDuration.

Or it could be more fine-grained for people who only care about errors and have a configuration like:

• beforeErrorDuration
• afterErrorDuration

This would enable users to customize the amount of data they wish to capture both before and after an error happens.

Product Area

Replays

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-replays for triage ⏲️

[bruno-garcia]

Moved this issue to the JavaScript SDK monorepo.

This sound like a fair configuration to me. To allow setting maxReplayDuration for a replay in case one would want that lower than 60 minutes.

We recently added an option called minReplayDuration that controls the min duration. Value in milliseconds, default is 5000 and max is 15000:

• Replay: Allow the user-defined minimum session duration before flushing #8562
• feat(replay): Ensure min/max duration when flushing #8596
• replay: minReplayDuration sentry-docs#7494

This seems like a specific use case worth adding an option for, that perhaps helps unblock some use cases where folks asked for a more generic way to 'filter' replays, such as:

• Provide a way to programmatically filter replays  #8462