The Issues page enables users to review all their frontend issues in one place and prioritize and learn more about the issues that are actually affecting the customer experience. The histogram at the top, visible when clicking the "See histogram" button, provides a quick snapshot of the health of your application by summarizing the number of sessions that are experiencing high-impact issues, low-impact issues, and no issues.

Currently, LogRocket's available issue types are JavaScript Errors, Network Errors, Rage Clicks, Dead Clicks, and Frustrating Network Requests, but we plan to expand into more issue types in the future (Network Error, Rage Click, Dead Click, and Frustrating Network Request issues are available for Pro plan customers only). You can toggle between these types or choose to view all with the dropdown in the upper righthand corner of the page.

  • JavaScript Errors - JavaScript Exceptions that are client-side. These errors may or may not directly impact the UI.
  • Network Errors - Failed network requests. These errors may or may not directly impact the UI.
  • Rage Clicks - Occurs when a user clicks repeatedly in frustration on an element.
  • Dead Clicks - Occurs when a user clicks on an interactive element (button, link, etc), but the click had no visible effect (ie. a DOM change).
  • Frustrating Network Requests - Compound events where a user shows impatient mouse actions during a particularly long network request.

Issues are retained for 1 month from the last instance of an issue. So if an issue stops occurring, it is available for 1 month after the last time it occurs. Issues retention is independent of an organization's session retention.

Issue status tabs

The status tabs separate the lists of issues based on prioritization, starting with "Needs Triage", or the issues that have yet to be given a status. High Impact, Low Impact, and Ignored issue lists can also be viewed by tabbing through this navigation.

Issue list

Below the status tabs, you'll see a list of Issues from across your application, along with some metadata about each issue.

To the right of the issue title and message, you'll see the prioritization level of the issue, as well as a frequency histogram of its occurrences. At the end of the row, you'll see some additional metadata, including the number of users and sessions the specific issue has affected.

Grouping issues

New issues will be automatically listed in the Needs Triage section of the page. From here, you can choose to group issues based on their severity and impact to the user.

In order to categorize an issue directly from here, click the dropdown next to Needs Triage in the issue row and select whether the issue is high-impact, low-impact, or should be ignored completely.

You'll then see the Change Issue Status modal appear. This allows you to add custom rules to group issues together and assign them the same status. You can choose to group based on the contents of the error message or the type of error. You can also assign the group a custom name.

Any new issues that arise within your application and match any of these rules will be auto-categorized into the selected status.

You can also categorize and group issues directly from their Issue Detail page.


Grouping issues must be of the same type

Please note that you can currently only group issues of the same type. For example, you can create groups that contain different types of JavaScript exceptions as well as groups that bundle different types of Network Errors, but you cannot create a group containing both of these types.

Feature Areas filter

In order to see issues that only occurred in specific areas of your app, use the Feature Areas filter. Once Feature Areas are selected, issues listed will be ones that have occurred within those Feature Areas (on those specific URLs) in your app.

Feature Areas use page Definitions (using the "Visited URL" filter). To add Feature Areas, either click the "Add New Feature Area" at the bottom of the Feature Area dropdown or go to the "Definitions" page and add new page Definitions.

Issue Detail page

You can click through on an individual issue to view more detailed information about the issue, including a sample playback of a user encountering the issue within a session. This is designed to give you information to help you categorize the severity and priority of the issue. For example, issues that block users within a critical sign-up or checkout flow may be deemed higher-priority than issues that occur silently with no real user impact.

The list to the left of the session playback shows the metadata associated with the specific session playback. The grey bars on the right-hand side represent cumulative information about the issue, such as frequency of occurrence, most common browser, and number of users and sessions impacted.

Below the playback is additional information related to the error. This includes stack traces if you have provided us with sourcemaps, and request and response information if the issue type is a network error.