AppDynamics Application Intelligence Platform

3.8.x Documentation



Release Notes

Use crash dashboards and crash snapshots to troubleshoot mobile application crashes.

Identifying Criteria of Applications that Crash Most Often

Sometimes most of your crashes share one or more criteria. In other words, your application crashes more often on certain devices or operating systems or carriers or connections.

To identify criteria of applications that crash

  1. In the left navigation pane click either End User Experience->iOS for iOS applications or End User Experience->Android for Android applications.
    The Mobile APM dashboard opens.
  2. Click the Crashes tab.
  3. Click the Dashboard subtab if it is not already selected.
  4. In the Crashes vs Requests graph, identify values that are significantly above the Average line. For example, if a device name is above the line, that type of device is experiencing more crashes than would be expected for the current load.
  5. Scroll down to the section for the criteria that seem to be experiencing more crashes.
  6. In the line graph, note the times that crashes spike. You can hover over a point on the graph to see the exact number of crashes at that time.
  7. Note the criteria (in this example the IPad 2 WIFI device) and the time that most crashes seem to occur.

Finding Causes of Crashes

After you have identified which applications are causing most of your crashes and approximately when most crashes occur, you can examine a few of those individual crashes to identify the cause.

To find root cause of individual crashes

  1. In the Crashes tab of Mobile APM Dashboard, click the Crash Snapshots subtab.
  2. Click Filters.
  3. Check the check box for the criteria of apps experiencing the most crashes that you identified in Identifying Criteria of Applications that Crash Most Often.
    This filters the crash snapshots list to display only snapshots of crashed applications meeting those criteria.
  4. In the crash snapshots list, select and double-click a snapshot that occurred around the time that most crashes occurred. In 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.
  5. Optional: Click Download to get a text version of the stack trace to send to your application development team.

Learn More


  • No labels