Use the Errors view to identify and analyze errors in your frontend applications.
Use the Errors view in your Frontend Launchpad to find and troubleshoot errors in your frontend application without writing queries. You can quickly see what the issue is, where it happened, and which users or sessions were affected.
The Errors view is available on the Web, iOS, and Android Launchpads.
The first section of the Errors view displays an overview of errors over the given time range. Next to the chart is a list of errors messages, sorted by the total number of times the error occurred over the time period.
Each bar on the chart represents the number of errors on each day during the given time period. The y-axis represents the number of errors. The x-axis represents points in time during the selected time range.
You can select an error on the chart and choose View Error Details.
The next section is a table of all the errors for the given time range, sorted by error count. Each entry includes the following data:
NSException or TypeError.You can search for specific errors by message or type using the search field above the table. Select an error message to view the error’s details.
Use filters to isolate errors across specific OS versions, devices, network speeds, and more. You can filter the Errors view with predefined or custom attributes using the Filter By menu at the top. Select Customize Filters at the bottom of the Filter By menu to create your own filters based on fields in your dataset.
In the Error Details view you can examine a specific error and jump to related errors with all the relevant data in one place.
The Error Details view starts with a summary of the error. Here you can see a chart of the error message over time, with the y-axis representing the number of times this error occurred, and the x-axis representing points in time during the selected time range.
Next to the chart, you can find the first and last times the error was seen relative to the selected time range. Beneath these are counts of how many users and/or sessions experienced the error during selected time period. The x-axis represents days.
Use the controls below the error summary to cycle between the oldest and latest occurrence of the error. You can search for attributes and your search will persist, so you can quickly check a specific attribute over the range errors.
The error message and the error stack trace are below the error summary.
If the stack trace has minified or obfuscated names and addresses, you can set up the symbolicator processor in your OpenTelemetry Collector pipeline. This processor replaces obfuscated symbols in your stack traces using debug information you provide.
A table of sessions with the same error message is at the bottom of the error details view. You can see how many errors occurred in the session and how many pages were affected. Selecting a Session ID will open a Timeline Analysis of that session.
