Troubleshooting¶

How to determine if the RUM SDK initialization is successful¶

1. Open the browser console:

1. Check if the object DATAFLUX_RUM exists:

Exists:

Does not exist:

1. Execute DATAFLUX_RUM.getInternalContext() to check if the object was initialized successfully:

If the initialization is successful, you can obtain object information such as the current application page's session, application, view, etc.

Initialization failure¶

1. If accessed via CDN, determine if the current application is an https site.
2. Confirm if the configuration is correct (including the format and names of the configuration parameters).

Initialization successful, but data is not reported or reported data is incomplete¶

1. Check the browser version information to determine if the corresponding data is supported according to the browser support list.
2. Check the initialization location of the RUM browser SDK and consider performing the initialization operation as early as possible in the application code.

XHR/FETCH requests are not associated with APM traces¶

Check if the allowedTracingOrigins configuration in the initialization config is enabled and confirm the format is correct. (If configured using regular expressions, ensure the array contains regex objects, not strings).

Correct ```js datafluxRum.init({ applicationId: '', datakitOrigin: '', env: 'production', version: '1.0.0', trackInteractions: true, allowedTracingOrigins: [/https:\/\/.*\.my-api-domain\.com/] // Regex should not have quotes })

Incorrect
 ```js
datafluxRum.init({
    applicationId: '<DATAFLUX_APPLICATION_ID>',
    datakitOrigin: '<DATAKIT ORIGIN>',
    env: 'production',
    version: '1.0.0',
    trackInteractions: true,
    allowedTracingOrigins: ["/https:\\/\\/.*\\.my-api-domain\\.com/"]
})

How to confirm successful association between APM and frontend XHR/FETCH requests¶

1. Open the browser console.
2. Check the Request Headers of the XHR/FETCH request to see if it contains the corresponding request header keywords information. The image below shows ddtrace-related request headers: