Enable data capturing for your mobile frontends in the New RUM Experience

• Latest Dynatrace
• How-to guide
• 5-min read
• Updated on Nov 12, 2025
• Preview

This guide provides essential information for setting up and utilizing the New RUM Experience for iOS and Android platforms. Follow the instructions below to ensure a smooth setup and optimal performance.

Enable the New RUM Experience for iOS and Android

Enable the New RUM Experience at the environment level

To enable the New RUM Experience for web frontends at the environment level

Set up your mobile app for New RUM Experience

Make sure you have the following settings in your app:

User events automatically reported to Grail (iOS and Android)

In the New RUM experience, RUM data is captured as user events, which are stored in the user.events table. The following user events are captured and stored in Grail:

ANR Reporting for mobile

With the New RUM Experience, Dynatrace automatically captures “Application Not Responding”(ANR) errors. ANRs are critical to monitor as they cause frustration to the user. The main problem is that the app's main thread, which is responsible for updating the UI, can't process user input events or draw, forcing the app to be closed.

These events are sent only if the mobile app is restarted within a timeframe of 10 minutes by the user.

By default, this feature is turned on. To turn it off use the following configuration options:

Android

OneAgent only reports ANR errors on devices with Android 11 or higher. On older Android versions, the ANR Error event is not available.

Using the ConfigurationBuilder when starting the agent manually:

public ConfigurationBuilder withAnrReporting(boolean enabled)

Using the DSL:

dynatrace {
  configurations {
    sampleConfig {
      anrReporting false
      ...
    }
  }
}

iOS

Using the dictionary configuration when starting the agent manually:

Dynatrace.startup(withConfig: ["DTXANRReportingEnabled": false, …])

Using the plist file:

<key>DTXANRReportingEnabled</key>
<false/>

React Native

Using the dynatrace.config.js file:

module.exports = {
    react: {
        ...
    },
    android: {
        // Those configs are copied 1:1
        config: `
        dynatrace {
            configurations {
                defaultConfig {
                    ...
                    anrReporting false
                }
            }
        }
        `
    },
    ios: {
        // Those configs are copied 1:1
        config: `
        ...
        <key>DTXANRReportingEnabled</key>
        <false/>
        `
    }

Flutter

Using the dynatrace.config.yaml file:

android:
  config:
    "dynatrace {
      configurations {
        defaultConfig {
          ...
          anrReporting false
        }
      }
    }"

ios:
  config:
    "...
    <key>DTXANRReportingEnabled</key>
    <false/>"

MAUI

Using the dynatrace.config.json file:

{
  "android": {
    "autoStart": {
      "beaconUrl": "https://...",
      "applicationId": "..."
    },
    "anrReporting": false
  },
  "ios": {
    "DTXBeaconUrl": "https://...",
    "DTXApplicationId": "...",
    "DTXANRReportingEnabled": false
  }
}

Native Crash Reporting for Android

Native crashes are crashes that originate in C/C++ code added via NDK. The official Android documentation lists examples and how to diagnose them.

With the New RUM Experience, Dynatrace automatically captures native crashes. Events are sent only if the mobile app is restarted within a timeframe of 10 minutes by the end user.

By default, this feature is turned on. To turn it off use the following configuration options:

Enable instant capturing of user events

Once new RUM is enabled for a mobile app monitored by Dynatrace, data is stored in Grail. On each end user device on which the mobile app is installed, the new configuration will be applied only after the first user session is finished. Upon the very first app start OneAgent will initiate non-Grail communication and upgrade to Grail only if ordered by server configuration, and only on the next app start.

Hence, the first session will be captured only on RUM Classic, unless the following build-time configuration is additionally applied:

Android

To avoid that and to start with Grail right away, the startupWithGrailEnabled flag must be set to true.

This can be done using the ConfigurationBuilder:

public ConfigurationBuilder withStartupWithGrailEnabled(boolean enabled)

Using the DSL:

dynatrace {
  configurations {
    sampleConfig {
      agentBehavior {
        startupWithGrailEnabled true
      }
    }
  }
}

iOS

To avoid that and to start with Grail right away, the DTXStartupWithGrailEnabled flag must be set to true.

This can be done in the .plist file:

<key>DTXStartupWithGrailEnabled</key>
<true/>

If the Dynatrace.startup(withConfig:) method is used, it needs to be added there.

Dynatrace.startup(withConfig: ["DTXStartupWithGrailEnabled": true, …])

React Native

Using the dynatrace.config.js file:

module.exports = {
    react: {
        ...
    },
    android: {
        // Those configs are copied 1:1
        config: `
        dynatrace {
          configurations {
            defaultConfig {
              ...
              agentBehavior {
                startupWithGrailEnabled true
              }
            }
          }
        }
        `
    },
    ios: {
        // Those configs are copied 1:1
        config: `
        ...
        <key>DTXStartupWithGrailEnabled</key>
        <true/>
        `
    }

Flutter

Using the dynatrace.config.yaml file:

android:
  config:
    "dynatrace {
      configurations {
        defaultConfig {
          ...
          agentBehavior {
            startupWithGrailEnabled true
          }
        }
      }
    }"

ios:
  config:
    "...
    <key>DTXStartupWithGrailEnabled</key>
    <true/>"

MAUI

Using the dynatrace.config.json file:

{
  "android": {
    "autoStart": {
      "beaconUrl": "https://...",
      "applicationId": "..."
    },
    "agentBehavior": {
      "startupWithGrailEnabled": true
    }
  },
  "ios": {
    "DTXBeaconUrl": "https://...",
    "DTXApplicationId": "...",
    "DTXStartupWithGrailEnabled": true
  }
}

Additional Android instructions

Add custom OkHttp client

OneAgent for Android now allows you to specify a custom OkHttp client to use for network requests, that are used to transmit RUM data to Grail.

This can be set using manual startup with the ConfigurationBuilder:

public ConfigurationBuilder withOkHttpClient(okhttp3.OkHttpClient httpClient)

Likewise, an OkHttp factory can be provided to achieve the same result:

public ConfigurationBuilder withOkHttpFactory(okhttp3.Call.Factory httpFactory)

Dependencies for Android

Additional iOS instructions

Dependencies for iOS

Agent

Swift Instrumentor

Unsupported features

Limitations