Monitor mobile crashes

Mobile crash aggregation

A crash happens when a user encounters an error and has to exit the app. App errors are all other types of errors that occur but don’t result in the user having to exit the app. For example, application not responding (ANR).

Splunk RUM's APPLICATION SUMMARY DASHBOARD groups errors by error ID. Each group's error ID is unique. For more information about the error ID, see About the error ID.

To see crashes from a specific mobile application:

  1. Scroll down to the application name and expand its section.

  2. n the expanded section, select the Crashes, App Errors, or All tab in the pane on the right. These tabs display aggregated data with a count of the number of crashes or errors in each aggregation.

  3. To see details about a specific crash or error, select it. This opens the Error groups side panel on the right.

  4. In the panel on the right, Splunk RUM displays the stack trace for this crash or error. If Splunk RUM has a mapping file (Android) or dSYM (iOS) for the application that this crash or error originated from, it displays the stack trace in readable form. Otherwise, it displays the message No mapping file detected (Android) or No dSYM detected (iOS).

View session details

The session details pane lists every session ID (span) that belongs to the user session you select. It also displays the entire timeline of the user session so that you have more insight into the events leading up to a crash. For example, you can see which views were loaded and what requests were made.

To see session details for a specific crash:

  1. Select that crash. This opens the Error groups side panel on the right.

  2. In the Error groups side panel, select the User Sessions tab. This opens the list of user sessions associated with the crash you selected.

  3. Select a specific session ID. This opens the Crash side panel with session details.

  4. If you've uploaded source mapping for your application, you can also see a human-readable stack trace: expand Stack Trace.

Explore top crashes across in Tag Spotlight

To open Tag Spotlight from Splunk RUM's APPLICATION SUMMARY DASHBOARD, select the All tab and then select the crash or error you're interested in. In Tag Spotlight you can explore application based errors, metrics, and events.

This image shows the crashed and app errors chart in the RUM overview dashboard.

To learn more about Tag Spotlight, see:

Connect source files

The information in most raw crash stack traces is not fully human-readable. To make a stack trace readable, you must provide platform-specific mapping information that translates that stack trace into human-readable form. You can either upload mapping information now ("on-demand") or as part of your application's CI pipeline:

  • To upload mapping files now, select Add dSYMs for iOS applications or Add a mapping file for Android applications.

  • To upload mapping files as part of your application's CI pipeline, see Add dSYMs for iOS applications or Add a mapping file for Android applications.