Configure the Splunk React Native RUM instrumentation 🔗

You can configure the Splunk Distribution of OpenTelemetry for React Native to add custom attributes, adapt the instrumentation to your environment and application, and more.

To configure the React Native RUM agent, add the key-value pairs to a ReactNativeConfiguration object. For example:

const RumConfig: ReactNativeConfiguration = {
   realm: '<realm>',
   rumAccessToken: '<rum-access-token>',
   applicationName: '<your-app-name>',
   environment: '<your-environment>',
   debug: true,
   /**
      * URLs that partially match any regex in ignoreUrls aren't traced.
      * URLs that are exact matches of strings in ignoreUrls aren't traced.
   */
   ignoreUrls: ['http://sampleurl.org'],
}

General settings 🔗

Use the following settings to configure the React Native RUM agent:

Option	Description
`beaconEndpoint`	Ingest URL to which the agent sends collected telemetry. The URL must contain your realm in Splunk Observability Cloud. For example, `https://rum-ingest.us0.signalfx.com/v1/rum` is the ingest URL for the `us0` realm.
`rumAccessToken`	RUM token that authorizes the agent to send telemetry data to Splunk Observability Cloud. To generate a RUM access token, see Generate your RUM access token in Splunk Observability Cloud.
`globalAttributes`	Sets additional attributes added to all spans. Attributes are defined as an array of comma-separated key-value pairs. For example: `["key1":"value1","key2":3]`. See Manage global attributes.
`environment`	Environment for all the spans produced by the application. For example, `dev`, `test`, or `prod`.
`ignoreUrls`	Regular expression pattern that matches URLs you want to ignore when reporting HTTP activity.
`debug`	Activates debug logging. The default value is `false`.

This page was last updated on May 30, 2023.

Was this topic useful?

Did you know that you can edit this page? Learn how!

Was this documentation topic helpful?

Enter your email address if you would like someone from the documentation team to reply to your question or suggestion.

Please provide your comments here. Ask a question or make a suggestion.

Comment should have a minimum of 5 characters and a maximum of 1,000 characters.

Feedback submitted, thank you! We resolve documentation feedback based on the severity of the issue reported, as well as an assessment of the potential number of customers who might be affected.

If you have a question about using Splunk software, we encourage you to check Splunk Answers or Splunk community Slack to see if similar questions have been answered, or to post your question for others to answer. If you have an active support entitlement and believe that your situation is caused by a product defect, file a support case in the Support portal https://login.splunk.com/page/sso_redirect?type=portal.

We are currently moving to a new documentation site. Expect a delay in responding to your feedback and applying any updates based on your feedback. Thank you for your patience and understanding while we work to bring you an improved documentation experience!