Troubleshooting¶

How to Verify RUM SDK Initialization¶

1. Open the browser console:

1. Check if the DATAFLUX_RUM object exists:

If it exists:

If it does not exist:

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

If initialization succeeded, you can retrieve the session, application, view and other objects for the current application page.

Initialization Failed¶

1. If you integrated via CDN, verify that the current application is served over https.
2. Check that the configuration is correct (including the format and names of the configuration parameters).

Initialization Succeeded but Data Is Not Reported or Is Incomplete¶

1. Check the browser version and refer to the browser support list to confirm whether the corresponding data type is supported.
2. Check where the RUM Browser SDK is initialized in your application code, and consider moving the initialization call as early as possible.

Session Replay Cannot Play¶

Page Shows "No Replay Data"¶

Check in order:

1. Whether sessionReplaySampleRate is greater than 0.
2. Whether startSessionReplayRecording() was called after the SDK was initialized.
3. Whether the current SDK version supports Session Replay.
4. Whether DataKit has session_replay_endpoints enabled.
5. If using a public DataWay, whether the client can reach the data upload endpoint.
6. Whether the current Session was excluded from replay data collection by the sampling policy.

Page Shows "Data Being Generated"¶

The replay data has entered the processing pipeline. Please refresh the page after a moment. If the status persists for a long time, check whether replay data is still being continuously uploaded.

Page Shows "Incomplete Replay Data"¶

Possible causes:

• Some data was not uploaded before the session ended.
• The user closed the page or application, causing cached data to not be sent in time.
• Client network issues.
• SDK initialization or recording started too late.
• Data upload was blocked by a proxy, firewall, or browser policy.

Page Shows "Status Query Error" or "Replay File Retrieval Error"¶

First refresh the page and try again. If the issue persists, record the Session ID, application ID, time of occurrence, and page error information, then contact technical support.

For integration and sampling configuration, see How to Integrate Session Replay. For the collection pipeline, recovery mechanism, and data gap classification, see Session Replay Collection Principles and Data Integrity.

XHR/FETCH Requests Are Not Correlated with APM Traces¶

Check whether the allowedTracingOrigins configuration is enabled in the initialization options and verify its format. (If configured as a regular expression, make sure 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 must not be quoted })

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 That APM and Front-End XHR/FETCH Are Correlated¶

1. Open the browser console.
2. In the XHR/FETCH request's Request Headers, check whether the corresponding header keys are present. The image below shows the ddtrace-related request headers: