Session Replay

This page contains an overview of the information available in the Session Replay sections of the Luciq Docs for iOS apps.

Features

Sessions List

Sessions are sorted chronologically by default. You’ll see the following information for each session:

  1. User Data: The end-user's email/name and ID. By default, it shows Luciq's UUID, but you can override it with your internal IDs using the User Identification API.

  2. Session Type: Any session that ends with a fatal crash or OOM is flagged as a crashing session. Any session that is affected by an App hang or a Force Restart is flagged as a frustrating session. Otherwise, a bucket is defined based on all the other metrics and occurrences (app launch, app traces, network, and UI hangs) that happened within the session. More examples can be found here.

  3. Session Issues: The issues that happened during the session. These include crashes, app hangs, slow app launches, screen loadings, or execution traces as well as Force Restarts. This can help you identify sessions that require your attention.

  4. Duration: The length of the replay.

  5. App Version: The app version the user was on during the session.

  6. OS: The OS version the device was on during the session.

  7. Date: of when the session has occurred.

Session Details

With each session, Luciq captures detailed information about the session itself. Below is the list of session related details that Luciq captures:

  1. User ID

  2. Date

  3. Session duration

  4. App version

  5. Device

  6. OS version

  7. User ID (if provided)

  8. Username (if provided)

  9. Locale

  10. Bundle ID

  11. Device location

  12. User attributes

  13. Feature flags

Timeline

A timeline from the beginning to the end of the session which visually highlights performance and stability issues that happen over the course of the replay. Users can easily move to the point on the timeline where they want to start debugging. It also visually shows the duration of the session.

Screenshots

Screenshots taken throughout the session whenever there is a change in the UI (The SDK captures a screenshot with every screen transition).

Logs

A whole host of logs are sent with every session. These logs include:

  1. Luciq Logs: Logs with various verbosity levels that you can add manually.

  2. User Steps: Log entries detailing each step the user has taken.

  3. Network Logs: Records of all network requests.

  4. Crashes: If Luciq’s Crash Reporting is enabled, you'll see all crash metrics within the session, including fatal crashes, app hangs, ANRs, and non-fatal errors.

  5. Performance: If Luciq's APM is enabled, you'll see all APM metrics for the session, including app launches, screen loading, flows, and networks.

Session Definition

A session starts when the app is brought into the foreground and ends when it moves to the background or when it's terminated either by the OS or the user.

Foreground Only

We currently support session replay for foreground sessions only.

User Identification

In order to find sessions by searching for specific users, make sure you use our user identification API. More details about the user identification API can be found here.

Last updated