Session replay | LaunchDarkly

This feature is for Early Access Program customers only

LaunchDarkly’s observability features are available to members of LaunchDarkly’s Early Access Program (EAP). To request early access, sign up here.

Overview

This topic explains how to use LaunchDarkly’s observability features to perform session replays. The Sessions view displays a list of recorded sessions. Use this view to perform session replays, which are repeatable explorations of an end user’s session in your application.

View session replays

To view a session replay, click Sessions in the left navigation menu, and then select a session from the list. Press the Play button to start the replay. Hover over or click on the colorful columns at the bottom of the screen to see different events in the session.

A session replay with event details expanded.

Search

To learn more about the search specification for the session replays view, read Search specification.

By default, the session replay SDK plugin automatically injects the following attributes to provide additional help with searching for sessions:

Attribute	Description	Example
`active_length`	Time the end user was active. Defaults to milliseconds. Use `s`, `m`, or `h` suffixes to designate seconds, minutes, or hours.	`10m`
`browser_name`	Browser the end user was using.	`Chrome`
`browser_version`	Browser version the end user was using.	`124.0.0.0`
`city`	City the end user was in.	`San Francisco`
`completed`	Whether the session has finished recording.	`true`
`country`	Country the end user was in.	`Greece`
`device_id`	Fingerprint of the end user’s device.	`1018613574`
`environment`	The environment specified in the SDK.	`production`
`first_time`	Whether this is the end user’s first session.	`false`
`has_comments`	Whether a LaunchDarkly member has commented on the session.	`true`
`has_errors`	Whether the session contains linked errors.	`true`
`has_rage_clicks`	Whether the end user rage clicked in the session.	`true`
`identified`	Whether the session successfully identified the end user.	`false`
`identifier`	The observability project ID passed to the session replay plugin initialization.	`1jdkoe52`
`ip`	The IP address of the end user.	`127.0.0.1`
`length`	The total length of the session. Defaults to milliseconds. Use `s`, `m`, or `h` suffixes to designate seconds, minutes, or hours.	`10m`
`os_name`	The end user’s operating system.	`Mac OS X`
`os_version`	The end user’s operating system version.	`10.15.7`
`pages_visited`	The number of pages visited in the session	`10`
`sample`	A unique order by which to sample sessions	`c1c9b1137183cbb1`
`service_version`	The version of the service specified in the session replay SDK plugin	`e1845285cb360410aee05c61dd0cc57f85afe6da`
`state`	The state the end user was in.	`Virginia`
`viewed_by_anyone`	Whether the session has been viewed by any LaunchDarkly member.	`true`
`viewed_by_me`	Whether you have viewed the session.	`false`

Privacy

Session replay supports privacy features, including data obfuscation and redaction. This ensures that sensitive data is not captured or displayed in the session replays. All of this functionality happens client-side, which means that no sensitive data is sent to LaunchDarkly servers. To learn more about the privacy options for session replay, read Privacy in the SDK documentation.

How is a session defined?

After a session starts, LaunchDarkly continues recording in the same session for up to four hours. Each browser tab or instance will start a distinct session, so if your web app is opened in two tabs at once, LaunchDarkly records two sessions.

However, after a session stops, it can be resumed. If your web app is opened in a single tab, closed, and then reopened within 15 minutes of closing, LaunchDarkly resumes the existing session. If more than 15 minutes have passed, LaunchDarkly starts a new session.