What Lucent imports
Lucent uses Sentry’s replay APIs for replay metadata and recording segments:- List an organization’s replays
- Retrieve a replay instance
- List recording segments
- Retrieve a recording segment
Requirements
You need:- a Sentry organization slug
- a Sentry project slug or project ID
- a Sentry auth token
- an optional environment filter, such as
production
org:read and project:read.
Connect Sentry
Enter your project details
Add your Sentry host, organization slug, project slug or ID, token, and
optional environment.
https://sentry.io. If you use a self-hosted Sentry
deployment, enter your own host.
Mobile and Expo replay support
Sentry web replay is supported. Sentry mobile and Expo replay import is beta:- DOM-like rrweb payloads pass through unchanged.
- screenshot-style mobile payloads are converted before video generation.
- wireframe-style mobile payloads are converted before video generation.
After import
Imported Sentry sessions keep their source metadata, so you can:- open the original replay link from the session detail view
- filter sessions and Signals by source
- filter Signals by feature flag values when available
Troubleshooting
| Problem | What to check |
|---|---|
| Lucent cannot save the integration | Confirm the token has org:read and project:read, and that the org and project slugs are correct. |
| No sessions import | Check the environment filter and confirm the project has Sentry replays in the selected time window. |
| A mobile replay is skipped | The replay did not contain renderable DOM, screenshot, or wireframe data. |