You can use Mobile RUM to investigate two different kinds of problems that can arise with your mobile applications: slow network requests and mobile application crashes.
Identify Your Slowest Network Request Types
To identify slow network requests:
Open the application in which you are interested.
In the left navigation bar, click Network Requests.
Select the Network Requests tab.
Click the top of the Network Request Time (ms) column, then toggle it to sort the network requests with the slowest ones at the top.
Skip over network requests that you expect to run for a long time or that have very little load (low Requests per Minute).
Select and double-click one of the slow network requests that you want to investigate.
In the network request dashboard, view the Key Performance Indicators at the top of the Network Request Dashboard. For example:
If the value for Network Request Time is large, the request or response body may be too large and is taking a while to transmit, or the data connection might be slow.
If the backend server is instrumented and the value for Total Server Time makes up a significant amount of the delay, scroll down to the Related Business Transactions section to investigate related business transactions on the server side.
Access Details of Individual Instances of Slow Requests
To investigate the cause of slow requests:
Select the Snapshots tab. The Snapshots List opens.
Click Filters.
In the Network Request Names dropdown under Network in the Filters panel, check the check box for the network request that you identified in Identify your slow network requests, then click Search. This restricts the list to snapshots for that network request only.
Click Filters again to close the filters panel.
In the list, click the top of the Network Request Time (ms) column, then toggle it to sort the network request snapshots with the slowest requests at the top.
Select and double-click one of the slow network requests. The network request snapshot displays the details of the slow request.
If this request is associated with a server-side application that is also instrumented, scroll down to see if transaction snapshots for this request are available on the server side. If transaction snapshots are available and if most of the time for this network request is spent on the server, click through to the related transaction snapshots to understand what is causing the slow performance on the server. See Transaction Snapshots.
Identify Applications that Crash the Most or Affect the Most Users
To troubleshoot mobile application crashes with crash dashboards and crash snapshots:
Open the application in which you are interested.
On the left navigation bar, click Crashes.
Select the Crash Dashboard tab.
Check the Unique Crashes list.
Sort either by Total Crashes or Impacted Users, depending on what you want to know. In the screenshot below, the list is sorted by impacted users.
View the Summary Crash Trend graph to discover particularly problematic time periods.
To find crashes in the problematic timeframe, click Analyze and drag up on the timeline where the most crashes occurred.
You should see the crash list reduced to those that occurred during the custom time period.
Double-click one of the unique crashes to open the Crash Details dialog.
From here, you can view the stack trace of the crash snapshot, note the thread and function in which the crash occurred. For some crashes, the crashed line number is also available. Optional: Click Download to get a text version of the stack trace to send to your application development team.
To access a complete data set for crashes that belong to this crash group, click Find Sessions. This opens the Mobile Sessions view with a filter for this Crash Group already selected.
