Docs » Data types collected by Splunk RUM

Data types collected by Splunk RUM 🔗

The following tables outline the types of data Splunk RUM collects.

Splunk RUM for Browser 🔗

When you instrument and configure Splunk RUM for Browser on your application, RUM collects the text in error.message and the full URL of each page in your application. Splunk RUM for Browser collects the following types of data about your application:

Data type

Description

Document load time

The average time it takes a to load a page

Full URL including query parameters

Does not including POST payloads, timing, and status codes

Console errors, including text of the error message produced by your app

  • Unhandled promise rejections

  • Document Object Model (DOM) errors on the document

  • Usage of console.error

  • Uncaught exceptions

XPath of relevant DOM elements

The button a user clicked

User metadata captured from headers sent on requests

  • User IP address

  • User location

  • User agent

Splunk RUM for Mobile: iOS 🔗

The Splunk RUM iOS library includes a Swift package that captures the following types of data about your iOS application:

Data type

Description

App life cycle events

App start up and app going to background

UI level events

Screen transitions and clicks on components

Network related events

Network changes, connection information. For example:
  • HTTP requests

  • Latency

  • Errors

Errors

Crashes and exceptions

Custom events

Events not captured by auto-instrumentation and any events that need manual work or coding.

Splunk RUM for Mobile: Android 🔗

The Splunk Android RUM library collects the following types of data about your mobile Android application:

Data type

Description

App life cycle events

App start up, app going to background transitions, and screen transitions, both for activities and fragments

Network related events

Network changes, connection information. For example:
  • HTTP requests

  • Latency

  • Errors

Errors and crash events

App crashes and exceptions

Custom events

Events not captured by auto instrumentation and any events that need manual work or coding

Application Not Responding (ANR) events

ANRs occur when the application does not respond to an input event after a certain amount of time