Skip to content

Troubleshooting

How to Confirm RUM SDK Initialization is Successful

  1. Open the browser console:

  1. Check if the DATAFLUX_RUM object exists:

Exist:

Not Exist:

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

If initialization is successful, you can obtain the session, application, view and other information of the current application page.

Initialization Failed

  1. If using CDN integration, confirm whether the current application is an https site.
  2. Confirm whether the configuration is correct, (including the format and name of the configuration parameters).

Initialization Successful, but Data is Not Reported or Reported Incompletely

  1. Check the browser version and confirm whether the data is supported according to the browser support list.
  2. Check the initialization position of the RUM browser SDK, and consider executing the initialization operation as early as possible in the application code.

Session Replay Cannot Play

Page Shows "No Replay Data"

Check the following items in order:

  1. Whether sessionReplaySampleRate is greater than 0.
  2. Whether startSessionReplayRecording() is called after SDK initialization.
  3. Whether the current SDK version supports Session Replay.
  4. Whether DataKit has session_replay_endpoints enabled.
  5. When using a public DataWay, whether the client can access the data upload address normally.
  6. Whether the current Session has not collected replay data due to sampling strategy.

Page Shows "Data is Being Generated"

This indicates that the replay data has entered the processing workflow. Please refresh the page later. If it takes too long, check whether the replay data is still being reported continuously.

Page Shows "Replay Data Incomplete"

Possible reasons:

  • Some data has not been reported before the session ends.
  • The user closes the page or application, causing cached data not to be sent in time.
  • Client network is abnormal.
  • SDK initialization or recording starts too late.
  • Data upload is blocked by proxies, firewalls, or browser policies.

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, occurrence time, and page error information, and contact technical support.

For integration and sampling configuration, please refer to How to Integrate Session Replay.

XHR/FETCH Requests are Not Correlated with APM Traces

Check whether the allowedTracingOrigins configuration is enabled in the initialization configuration, and confirm the format is correct. (If configured with a regex, ensure that the array contains a regex expression, not a string)

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 APM and Frontend XHR/FETCH are Correlated Successfully

  1. Open the browser console.
  2. Confirm whether the Request Headers of the XHR/FETCH request contain the corresponding request header keywords. The following image shows the relevant headers for ddtrace: