• English日本語한국어
  • 로그인지금 시작하기

Crash analysis: Group and filter your crashes

Mobile app crashes can result in users submitting negative reviews, which can affect your organization's reputation. Crashes can also result in users deleting your app altogether, which affects your organization's profitability. With the Crash analysis page, you can identify and deal with one of the largest bottlenecks in the development lifecycle: the time it takes to resolve unanticipated exceptions.

Use crash analysis features

When your development team receives an emailed crash notification, they can select the email link to review detailed information about the crash in our user interface, or analyze chart data directly through a query. The individual Crash details page also includes tracking tools for your team to follow the issue from reporting to resolution.

Our Crash analysis page helps developers:

  • Slice and dice your crash and network data (using groups and filters) to analyze trends leading to the crash.
  • Understand a particular user's experience by using a custom attribute.
  • Pinpoint when most crashes occur; for example, by filtering by Last Interaction, or by viewing the event trail on the Crash type summary page.
  • Align issues with common characteristics in networks or devices.
  • Examine specific problems in a crash report that may be buried in thread breakdown data, trace details, or the trail of user interactions in the crashed session.
  • Quickly see trends from the Crash profiles tab.

View the crash list

To view the filterable Crash list in the New Relic UI:

  1. Go to one.newrelic.com > All capabilities > Mobile > (select an app) > Exceptions > Crash analysis.

    OR

    To view the filterable Crash analysis page directly from the mobile app's Summary page, select the Crash occurrences chart's title.

  2. Use any of our standard page functions to drill down into detailed information, such as zooming into any area of a chart.

Use the crash analysis workflow

To get the most out of mobile monitoring's Crash analysis UI, use this basic workflow.

  1. Start with the Crash rate percentage and Crash-free users percentage charts to see at a glance whether there are any unexpected spikes, dips, or patterns with crash time frames, or uneventful periods within the selected time period.
  2. Use the groups and filters to examine attributes (for crashes, devices, locations, or other custom attributes) in more detail.
  3. The Top 20 occurrences chart lets you identify broad patterns about the occurrences you chose from groups and filters. You can correlate these patterns, or you can find information like crash percentages during the chosen time period.
  4. Optional: Query or share the chart data.
  5. Look for patterns in the Crash location table information, including location, exception type, date and number of occurrences, version, and number of users affected by the crash.
  6. Select a crash report from the table to view its interaction trail, its event trail, thread details for individual occurrences, attributes, and more. If necessary, resymbolicate or export the crash details to Xcode so you can debug your source code more easily.
  7. When finished, mark the crash occurrences as Resolved.

Resolved crashes include a banner identifying who resolved the crash and when. Based on mobile monitoring's data retention policies, you can filter by resolved crashes when you need to track back to historical information.

Configure crash report email settings

To learn how to configure email settings, see Email settings.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.