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 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.
Below the histogram, 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 a status section with 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.
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
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.
Updated 4 days ago