LogRocket

Rationale

We use LogRocket as one of our error-tracking tools. It allows us to get data-sanitized insights into user actions, error codes, requests, responses, and more by recording users' screens, making it easy to reproduce problems. With filters and integrations with customer support, issue management, and observability tools, we could find any user session and understand the problems users encounter.

The main reasons why we chose it over other alternatives are:

1. It provides important metrics like user frustration and user success.
2. It gives detailed data related to requests and responses.
3. It integrates very well with other tools of our stack.
4. It is easy to set up and also very lightweight.
5. It is entirely prepared for developers.
6. It provides essential debugging tools.

Alternatives

The following alternatives were considered but not chosen for the following reasons:

1. Zoho PageSense: It does not provide the same detailed debugging capabilities as LogRocket.
2. Heap: It does not provide a better session replay.
3. Hotjar: It shows where users are having trouble but it does not show as much information about why those issues are happening.
4. Matomo: It does not provide the same real-time user event tracking and debugging capabilities.
5. FullStory: It does not provide as detailed insights into JavaScript errors.

Usage

We use LogRocket for:

1. View user session replays to understand errors.
2. Measure customer success.
3. Set up and manage custom dashboards for metrics of interest.
4. Identify and debug issues.
5. Get metrics about our components' behavior and how the clients are experiencing them.
6. Visualize heatmaps.
7. Analyze common user journeys.
8. Analyze converse funnels.

We do not use LogRocket for:

1. Galileo AI.
2. LogRocket Feedback.

Guidelines

You can access the LogRocket hub by entering the LogRocket application through Okta. There, you can navigate through the different dashboards, search for user sessions, and debug issues.