Error Inspector

  • Latest Dynatrace
  • Overview
  • 4min
  • Preview

Error Inspector is an advanced application within the Dynatrace platform designed to help developers and IT teams discover, track, and investigate front-end errors in web and mobile applications. Error Inspector provides comprehensive insights into the errors affecting your users, enabling you to enhance the reliability and performance of your applications.

  1. Join the New RUM Experience preview.

  2. Enable New RUM Experience.

    See New RUM Experience settings

Overview page

The Overview page shows several charts to analyze the number and context of errors. Error counts are provided over time (split by monitored frontends) and grouped by the reported dimensions, such as browser type, operating system, and URL provider type. Analyzed errors can be filtered using the quick filter bar on the left or selecting a dimension in a chart via context menu. All charts provide several options for manual investigation of the shown data. The following options are available:

  1. Edit in Notebook: Opens the Notebook app and adds a corresponding query section to a notebook.
  2. Pin to dashboard: Adds the chart to a Dynatrace Dashboard.
  3. Open With: Exports the underlying DQL query to a selected app.

Explore errors over time

This chart provides an overview of the error count and distribution over the selected timeframe. The shown error count is either split by the top 10 frontends that report the errors, or split by the error type, such as request error, exception, or csp error.

Errors by Error Type

This chart shows a breakdown of errors by error type. Possible values for error.type are listed in Global field reference - Error.

Errors by Operating System

This chart shows a breakdown of errors by operating system that runs the monitored frontend. The os.name field is documented in Global field reference - OS.

Errors by URL provider

This chart shows a breakdown of errors by URL provider type, such as first party or third party. The url.provider field is documented in Global field reference - URL.

Errors by Browser (Web only)

This chart shows a breakdown of errors by browser name. The browser.name field is documented in Global field reference - Browser.

Errors by User Type (Web only)

This chart shows a breakdown of errors by user type (real_user, robot, synthetic) name. The dt.rum.user_type field is documented in Global field reference - Dynatrace RUM.

Errors by App Short Version (Mobile only)

This chart shows a breakdown of errors by app version. The app.short_version field is documented in Global field reference - App.

Explorer page

On the Explorer page, error instances are grouped across all monitored frontends. Each column provides information to help you understand the impact of each error on your end users. Errors are automatically sorted by the highest number of affected users. The menu in the upper-right corner of the table offers the following options:

  • Edit in notebook adds the query to a notebook in Notebooks Notebooks.
  • Pin to dashboard adds the errors table to a dashboard in Dashboards Dashboards.

The Explorer page provides you with the following capabilities:

Filter errors

You can filter errors based on various criteria, such as error type, front-end application, and operating system. Filter settings are persisted in the URL, allowing you to share filtered analyses with authorized colleagues by simply copying and sharing the URL.

Investigate an error

Select an error to view its details and context, including distribution patterns. For example, you can identify and resolve an error affecting multiple front-end applications to improve the user experience across all affected applications. Developers can create JIRA tickets directly from any error, if you've set up the JIRA for Workflows app.

Stack traces are provided for exceptions and crashes. Note that source maps or symbol files need to obtain readable (de-obfuscated stack traces), as explained in the following section.

Upload source maps and symbol files

To obtain readable stack traces, you need to provide source maps or symbol files. You must upload them using our REST API or the classic UI. See the Dynatrace API documentation for more details.

The JavaScript API is not yet publicly documented. To access it:

  1. Go to Dynatrace.
  2. In the platform search, type API. In the search results, see Support resources section and Dynatrace API below it.
  3. Select Dynatrace API to access the Dynatrace API documentation. A new page opens with the Dynatrace API definitions.
  4. In the upper right corner, go to Select a definition.
  5. From the drop-down list, choose Classic Environment API v2 and scroll to JavaScript mapping files.

Analyze and filter affected pages

The Affected pages table shows the web pages that are affected by the error. Moreover, a filter for page can be added.

Check error occurrences in Session Details and Traces

Part of the Error Inspector preview is the possibility of seeing sessions where an investigated error occurred to better understand the user perspective and give additional context to the errors they investigate. The Session Details view will soon become part of the Users & Sessions app. However, during preview, it's available as a standalone feature.

To start using it, go to Dynatrace Hub and install the Session Details application. After that, the new application will be visible on a list of your applications. However, in its current shape, this application doesn't allow you to browse sessions. To do that, you need to go to Error Inspector and open the error you're interested in. Then, in the Ocurrences table, select your session from the Session ID column to see the session details as an overlay.

The Ocurrences table also links to the related traces (if available) in Distributed Tracing Distributed Tracing.

Related tags
Digital ExperienceError InspectorError Inspector