Replay Page and Filters
If you have any questions, feedback or would like to report a bug, please open a GitHub issue with a link to a relevant replay or, if possible, a publicly accessible URL to the page you're attempting to record a replay of.
You can search for or browse replays of user sessions on the Replay page, where they’re organized chronologically by default. You’ll see the following information for each session:
- Project: The project in which the session was recorded.
- Start Time: How long ago the replay was triggered. (Replays can appear here while the recording is still in progress.)
- Duration: The length of the replay. (Recordings can range from 1 second to 60 minutes.)
- Errors: The number of frontend errors identified by Sentry, as encountered in the replay. (Sometimes the error count reported is different from the actual errors captured. Read more in Error Linking.)
- Activity: The activity level as determined by the number of errors encountered, their duration, and the number of UI events.
By default, the IP address is used to identify each replay on this page. This can be changed in your organization and project settings. If you’d like to set an email or a username instead, call Sentry.setUser() in your client-side configuration.If you’ve enabled the option to “Prevent Storing of IP Addresses” in either your project-level or organization-wide settings, the IP address will appear redacted on the Replay page. For more information, read about several data scrubbing options in the Sentry app on either an organization-wide or a project level.
Replays can appear on this page while they’re still in progress. You can’t delete in-progress replays.
Each replay will bring users to the Replay Details page.
All replays have built-in key fields, and may have custom tags if you have them set up. The search bar operates similarly to the one in the Discover Query Builder. Use it to enter these keys and assign them values. This will filter down your list of replays so you can quickly find the ones with the criteria you care about. For example, you can refine your replays search to a specific browser by using
browser.version: as a key field and assigning the version as a value. For a list of all the built-in key fields/replay properties, check out our Searchable Properties documentation.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").