RUM Android Advanced Configuration

RUM Android Advanced Configuration

If you have not set up the SDK yet, follow the in-app setup instructions or refer to the Android RUM setup documentation.

Enrich user sessions

Android RUM automatically tracks attributes such as user activity, screens, errors, and network requests. See the RUM Data Collection documentation to learn about the RUM events and default attributes. You can further enrich user session information and gain finer control over the attributes collected by tracking custom events.

Custom Views

In addition to tracking views automatically, you can also track specific distinct views (activities, fragments, etc.) when they become visible and interactive in the onResume() lifecycle. Stop tracking when the view is no longer visible. Most often, this method should be called in the frontmost Activity or Fragment:

   fun onResume() {
     GlobalRum.get().startView(viewKey, viewName, viewAttributes)        
   fun onPause() {
     GlobalRum.get().stopView(viewKey, viewAttributes)        

Add your own performance timing

In addition to RUM’s default attributes, you can measure where your application is spending its time by using the addTiming API. The timing measure is relative to the start of the current RUM view. For example, you can time how long it takes for your hero image to appear:

    fun onHeroImageLoaded() {

Once the timing is sent, the timing will be accessible as @view.custom_timings.<timing_name> (For example, @view.custom_timings.hero_image). You must create a measure before graphing it in RUM analytics or in dashboards.

Custom Actions

In addition to tracking actions automatically, you can also track specific custom user actions (taps, clicks, scrolls, etc.) with RumMonitor#addUserAction. For continuous action tracking (for example, tracking a user scrolling a list), use RumMonitor#startUserAction and RumMonitor#stopUserAction.

   fun onUserInteraction() {
     GlobalRum.get().addUserAction(resourceKey, method, url, resourceAttributes)

Custom Resources

In addition to tracking resources automatically, you can also track specific custom resources (network requests, third party provider APIs, etc.) with methods (GET, POST, etc.) while loading the resource with RumMonitor#startResource. Stop tracking with RumMonitor#stopResource when it is fully loaded, or RumMonitor#stopResourceWithError if an error occurs while loading the resource.

   fun loadResource() {
     GlobalRum.get().startResource(resourceKey, method, url, resourceAttributes)
     try {
       // do load the resource
       GlobalRum.get().stopResource(resourceKey, resourceKind, additionalAttributes)
     } catch (e: Exception) {
       GlobalRum.get().stopResourceWithError(resourceKey, message, origin, e)

Custom Errors

To track specific errors, notify the monitor when an error occurs with the message, source, exception, and additional attributes. Refer to the Error Attributes documentation.

   GlobalRum.get().addError(message, source, throwable, attributes)

Track custom global attributes

In addition to the default RUM attributes captured by the mobile SDK automatically, you can choose to add additional contextual information, such as custom attributes, to your RUM events to enrich your observability within Datadog. Custom attributes allow you to slice and dice information about observed user behavior (such as cart value, merchant tier, or ad campaign) with code-level information (such as backend services, session timeline, error logs, and network health).

Track User Sessions

Adding user information to your RUM sessions makes it easy to:

  • Follow the journey of a given user
  • Know which users are the most impacted by errors
  • Monitor performance for your most important users

The following attributes are optional, you should provide at least one of them:

usr.idStringUnique user identifier.
usr.nameStringUser friendly name, displayed by default in the RUM UI.
usr.emailStringUser email, displayed in the RUM UI if the user name is not present. It is also used to fetch Gravatars.

To identify user sessions, use the setUser API, for example:

Datadog.setUserInfo('1234', 'John Doe', '')

Track attributes

   // Adds an attribute to all future RUM events
   GlobalRum.addAttribute(key, value)

   // Removes an attribute to all future RUM events

Track widgets

Widgets are not automatically tracked with the SDK. To send UI interactions from your widgets manually, call the Datadog API. See example.

Initialization parameters

You can use the following methods in Configuration.Builder when creating the Datadog configuration to initialize the library:

Enables tracking user interactions (such as tap, scroll, or swipe). The parameter also allows you to add custom attributes to the RUM Action events based on the widget with which the user interacted.
Defines the strategy used to track views. Depending on your application’s architecture, you can choose one of several implementations of ViewTrackingStrategy or implement your own.
addPlugin(DatadogPlugin, Feature)
Adds a plugin implementation for a specific feature (CRASH, LOG, TRACE, RUM). The plugin is registered once the feature is initialized and unregistered when the feature is stopped.
Enables tracking tasks taking longer than durationThreshold on the main thread as long tasks in Datadog.
Defines hosts that have tracing enabled and have RUM resources categorized as first-party.
Switches target data to EU endpoints.
Switches target data to US endpoints.
Switches target data to US1-FED endpoints.
Defines the individual batch size for requests sent to Datadog.
Defines the frequency for requests made to Datadog endpoints (if requests are available).
Sets the RUM sessions sampling rate. (A value of 0 means no RUM events are sent. A value of 100 means all sessions are kept.)
Sets the data scrubbing callbacks for views, actions, resources, and errors.

Automatically track views

To automatically track your views (activities, fragments, etc.), provide a tracking strategy at initialization. Depending on your application’s architecture, you can choose one of the following strategies:

Every activity in your application is considered a distinct view.
Every fragment in your application is considered a distinct view.
Every activity or fragment in your application is considered a distinct view.
Recommended for Android Jetpack Navigation library users. Each Navigation destination is considered a distinct view.

For instance, to set each fragment as a distinct view, use the following configuration in your setup:

val configuration = Configuration.Builder(rumEnabled = true, ...)

Tip: For ActivityViewTrackingStrategy, FragmentViewTrackingStrategy, or MixedViewTrackingStrategy you can filter which Fragment or Activity is tracked as a RUM View by providing a ComponentPredicate implementation in the constructor.

Note: By default, the library does not track any views. If you decide not to provide a view tracking strategy, you must manually send the views by calling the startView and stopView methods yourself.

Automatically track network requests

To get timing information in resources (third-party providers, network requests) such as time to first byte or DNS resolution, customize the okHttpClient to add the EventListener factory:

val okHttpClient = OkHttpClient.Builder()

Automatically track long tasks

Long running operations performed on the main thread can impact the visual performance and reactivity of your application. To track these operations, define the duration threshold above which a task is considered too long.

val config = Configuration.Builder(rumEnabled = true, ...)

Modify or drop RUM events

To modify some attributes in your RUM events, or to drop some of the events entirely before batching, provide an implementation of EventMapper<T> when initializing the SDK:

val config = Configuration.Builder(rumEnabled = true, ...)

As you will notice when implementing the EventMapper<T> interface, only some of the attributes are modifiable for each event type as follows:

Event typeAttribute keyDescription
ViewEventview.referrerURL that linked to the initial view of the page
view.urlURL of the view
view.nameName of the view
ActionEvent name
view.referrerURL that linked to the initial view of the page
view.urlURL of the view
view.nameName of the view
error.messageError message
error.stackStacktrace of the error
error.resource.urlURL of the resource
view.referrerURL that linked to the initial view of the page
view.urlURL of the view
view.nameName of the view
resource.urlURL of the resource
view.referrerURL that linked to the initial view of the page
view.urlURL of the view
view.nameName of the view
view.referrerURL that linked to the initial view of the page
view.urlURL of the view
view.nameName of the view

Note: If you return null from the EventMapper<T> implementation, the event is dropped.

Further Reading

Additional helpful documentation, links, and articles: