Created by Unknown User (delling@appdynamics.com), last modified by Unknown User (ellen.evans@appdynamics.com) on Jul 28, 2014

Crash snapshots provide detailed information on a single application crash.

Content of Crash Snapshots

The left side of the snapshot displays the key properties of the snapshot, such as the application that crashed, the time of the crash, the exception thrown when the application crashed, the function running when the application crashed, the file containing the crashed function, the line number on which the application crashed. Sometimes not all of this information is available.

The right side of the snapshot displays the call stack of the crashed application, showing the thread in which the crash occurred. This is the full stack trace for this specific crash, not the aggregated stack trace shown in the crash group dashboard.

If the information in the stack trace is cryptic, it is possible that source code for your iOS app was not symbolicated or the source code for your Android app was obfuscated. See Get Human-Readable Crash Snapshots for information about why this happens and what you can do about it.

Click Download to grab the stack trace in a file that you can forward to developers.

Archiving Crash Snapshots

Normally crash snapshots are purged after two weeks. You can archive a snapshot beyond the normal snapshot lifespan to retain it for future analysis.

To archive a snapshot, click the Archive button in the upper right corner of the snapshot window.

You can also archive crash snapshots from the crash snapshots list.

You can view archived snapshots by checking Archived as a view option in the crash snapshots list.

Customers with on-premise controllers can modify the default two-week period by configuring the events.retention.period in the Controller Settings section of the Administration console.