Skip to content

Troubleshooting

This article provides troubleshooting suggestions for C++ SDK initialization exceptions, no data, and compatibility issues.

No Data After Initialization

Please check the following items first:

  1. Whether the DataKit installation, RUM collector configuration, and IP geolocation database installation in the Prerequisites have been completed
  2. Whether the address configured in FTSDKConfig.setServerUrl is accessible from the current device
  3. Whether FTRUMConfig.setRumAppId is filled in correctly
  4. Whether sdk->install(...), sdk->initRUMWithConfig(...), and the corresponding Log / Trace initialization methods have been called
  5. Whether View, Action, Resource, Error, LongTask, or Log has been actually triggered during the program lifecycle

Debug Log Check

Debug logs can be enabled via ft_sdk_config.json:

{
  "general_config": {
    "enable_sdk_log": true
  }
}

It is recommended to first keep only the SDK initialization and one manual report in a minimal example. After confirming the basic link is available, gradually add business logic.

No RUM Data

Please confirm:

  • setRumAppId has been set correctly
  • sdk->initRUMWithConfig(...) has been executed
  • RUM collection interfaces have been manually called. For details, please refer to Custom Collection Rules
  • setSamplingRate is not set to 0

No Log or Trace Data

Please confirm:

  • sdk->initLogWithConfig(...) and sdk->initTraceWithConfig(...) have been executed respectively
  • Log has enabled setEnableCustomLog(true)
  • Trace has set the correct setTraceType(...) according to the backend link type
  • If you need to associate RUM in logs and links, please enable setEnableLinkRUMData(true)

Compatibility Notes

The current C++ SDK documentation explicitly supports the following platforms:

  • Windows
  • Linux

If the current runtime environment is not within the above scope, it is recommended to first confirm the SDK version and platform support, and then evaluate the access solution.

Custom Field Conflicts

If reported fields are abnormal or overwritten, please check if they have the same name as the SDK's built-in fields. Please read the Conflict Field Description for naming rules.