Attention: As of July 2024, Cloud Diagnostics Advanced is officially deprecated. It will be sunset in Q3 2025, and current customers will be supported through the end of their current annual subscription. Contact us if you are interested in a crash and error reporting tool.

Overview

The Overview page provides an ‘at a glance’ view of your project’s health by displaying different top down views of your error / crash data. The widgets in place were designed to serve that goal by enabling a number of important use cases:

  • Top down synthesis: Aggregate widgets allow developers or project leads to quickly see their application's stability and how many total, unique, and open errors have been reported in their project for a fast, simple status update
  • Application stability over time: Users can visualize their error count through time, by application version to monitor their app’s stability across releases.
  • Error distributions across customizable attributes: The stacked bar chart widgets at the bottom of the page show how your errors are distributed across relevant attribute values. For example, errors by operating system, classifiers, etc. Note that these can be configured to distribute by any indexed attribute to allow users to customize the page to fit their needs. See below for more information.
  • Filter the overview: As with the Explore, Triage, and Debug views, the Overview page can also be manipulated using the global filter bar to suit your specific needs.

Errors over time

On the Overview page, you’ll have access to one of our new visualization tools: A line chart that shows your project’s errors through time, by version. This tool makes it easy to see if a particular build is problematic and is great for monitoring a new release.

If you want to see the total error count through time, you can use the dropdown in the top-right corner of the widget to toggle between “Total” and “By version” modes.

Customize the version attribute

You can customize the version attribute used by the error over time by version widget. For example, you can use custom attributes to identify the build version, the app version, or the programming language version.

To change the version attribute used by the Overview page, click the pencil icon to the right of the relevant widget’s title as shown below.

Error distribution by attribute

The stacked bar chart widgets at the bottom of the Overview page allow you to see a quick breakdown of their errors across different attributes. These widgets are a great way to quickly identify an issue that may be specific to an operating system, device type, or any other relevant attribute.

The Overview page also integrates with the other views. If a distribution widget surfaces something worth investigating further, you can click the "Analyze In Explore" link at the top right of the widget. This will take you to the Explore view, where you can view more details.

Stability metrics widgets

As of version 3.19.25, the Overview page also supports "Error-free sessions" and "Error-free users" metrics to measure your project’s stability and user experience:

  • Error-free sessions: Displays the percent of total application sessions that experienced no errors.
  • Error-free users: Shows the percentage of unique users who did not encounter any errors.

Note that these widgets will respond to filters so if you want to see "Crash-free" metrics instead, you can filter out Non-Crash errors using the global filter bar. For example, error.type = Crash.

Error-free sessions over time

The error-free sessions over time line chart is a time view of the error-free sessions widget mentioned above. It shows the % of sessions in which there were no error reports received, bucketed and plotted through time.

The bucket size for each point on the line chart will vary as you adjust the global filter bar's time frame. For example, if you’re looking at a time frame of the past 30 days, each point will represent one day, whereas when looking at the past 7 days each point represents a 12 hour period.

Supported platforms

See the table below for platform support and limitations.

Feature supportAndroid™iOSWindowsMacOSWebGLPlayStation®4/PlayStation®5Nintendo Switch™Xbox® One/Series X
Managed exceptionsYesYesYesYesYesYesYesYes
AttachmentsYesYesYesYesYesYesYesYes
BreadcrumbsYesYesYesYesYesYesNoYes
Offline databaseYesYesYesYesYesYesNoYes
Native crashesYesYesYesNoNoYesYesYes
HangsYesYesYesNoNoNoNoNo
Out of memory crashesYesYesPartialNoNoNoNoNo

Note: To enable native crashes for PlayStation® or Nintendo Switch™, the user must pass credentials information to third-party services. Then all detected crashes available through the Platform partner or Unity will be downloaded and sent to Backtrace in order.