Cloud Diagnostics Advanced is powered by Backtrace, a Sauce Labs company.

Try Cloud Diagnostics Advanced for free

Get started with Cloud Diagnostics Advanced using our free tier available on the Unity Store.

The free tier includes support for mobile, PC, online (including webGL), consoles, and servers, and is limited to:

  • 1 seat / year
  • 25k errors
  • 30 days error retention
  • 10GB storage

Supported platforms

Supported platformsSupported systems
MobileAndroid™, iOS
PCWindows, MacOS, Linux
Game consolesPlayStation®4, PlayStation®5, Xbox® One, Xbox® Series X, Nintendo Switch™

Note: Offline database capabilities are not supported for Nintendo Switch.

Access your Cloud Diagnostics Advanced subscription

Follow these steps to gain access to your Cloud Diagnostics Advanced dashboard before setting up in the Unity Editor and collecting errors.

Cloud Diagnostics Advanced subscriptions are seat-based, so the user must be:

  1. A member of the Organization the subscription was purchased for.
  2. Assigned a seat of the relevant subscription in the Organization.
  3. If the member has a User or Guest role within the organization, they must be assigned to the specific project(s).

Get started with Cloud Diagnostics Advanced

Once Cloud Diagnostics Advanced is set up, you can view crash and error reports from the Unity Dashboard:

  1. Sign in to the Unity Dashboard with your Unity ID.
  2. Select the relevant project.
  3. From the main navigation menu, select LiveOps > Cloud Diagnostics Advanced > Diagnostic.

There are three key navigational components to help you analyze your error and crash data:

  • Filters: Define your working set. Specify time frames and additional criteria to indicate which errors and fingerprints to analyze.
  • Saved views: Commonly used filters for quick access and sharing for the selected project.
  • Tools and results list: Triage, Explore, and Debug to prioritize, analyze, and debug your crashes.


Time frame filters

On the top-left in the image above, there are filters for Time Frame. You can filter for issues that have occurred during a certain time period, or when an issue was first seen, to identify when an issue originated.

Filter operators

You can add filters identifying crashes from a certain version, a certain user, specific operating system, or more. Filters are available on any system or custom metadata that you provide with your crashes. Filter operators include not-contains, regular-expression, inverse-regular-expression, at-least, or at-most, depending on the data type. See the image below for examples of the different operators available.

Case insensitive filters

By default, all search operators are case sensitive. If you want to search using case insensitivity, enter a regex or inverse regex within /{your-search}/i to invoke case insensitive search.

For example, if you know a user input description is banana or Banana or BaNaNa, you could enter regular-expression /banana/i and any of those would be included.

Aggregation filters

Use aggregation filters to apply an additional filter on the results based on an aggregation, such as a unique count, or a minimum or maximum from a series of values. Below are some example questions you can ask with this feature:

  • "Show me crashes that have impacted at least 10 unique servers."
  • “Show me crashes that were likely introduced in version 2.1.0.”
  • "Show me crashes that have occurred in at least 2 release channels.”
  • "Show me crashes that have impacted at most 1 unique scene in the game, so we can hone in on specific scene impacting issues."

Tools and result lists

After defining your working set, choose a tool to view and manage the result list. We'll view the result list in the context of the triage tool here.

The result list varies vary depending on which tool you use. We use the Triage tool result list in the examples below, but see the different capabilities offered in Explore and Debug as well.

At the top of the result list, there are some informational text that tells you how many issues are displayed and the total. This gives you a view of how many additional crashes or errors that are identified outside the filter window.

Depending on which tool you use, you have additional ways to manipulate the result list and continue your exploration of error data:

  • In the Triage tool, errors are grouped by fingerprint. Actions are available to resolve the error, and you can open a detailed view for the fingerprint to offer more introspection into the aggregate information.
  • In the Explore tool, choose which attributes to group by, for more robust exploration of your error data. Common groupings are: by user ID (to see impact by user), host or device ID (to see impact to each host), OS version (to identify issues encountered after an OS patch), or any custom attributes useful for your application.
  • In the Debug tool, navigate through all individual errors that are returned based on the filter conditions. You can iterate through a group of similar errors to identify additional trends or commonalities.