Help Center > > User Guide> Management Platform> Device Management> Devices> Device Details> Message Tracing

Message Tracing

Updated at: Sep 02, 2019 GMT+08:00

On the device list, click a device to open the Device Details page.

The message tracing function can be used to quickly locate and analyze faults when a fault occurs in device binding, command delivery, data reporting, device information update, and device monitoring. The IoT platform supports message tracing for NB-IoT and MQTT devices. Up to 10 devices bound to an application can be traced simultaneously.

Enabling Message Tracing

  1. Log in to the Management Portal, click Device Management on the upper navigation bar, and choose Devices > Device List in the navigation tree.
  2. Search for the device to be traced and click the device to open the device details page.
  3. On the Message Tracing tab page, click Start or Restart. In the dialog box displayed, set the message tracing duration, and click Confirm. The message tracing duration starts from the time at which the task starts, and messages generated thereafter are traced. If you click Restart, the time restarts.


    If you start the message tracing again, the historical data of the last message tracing is cleared.

    Figure 1 Start Message Tracing dialog box

Figure 2 shows example tracing results. The tracing records with the same serial number are the result of one service processing. In the following information:

  • Blue text: indicates that the node successfully processes the message.
  • Red text: indicates that the node fails to process the message. You can click next to a tracing record to view its details and locate and analyze the fault based on the failure handling suggestions.
Figure 2 Message tracing results

After starting a message tracing task, the IoT platform traces messages in the following scenarios: device binding, command delivery, data reporting, device information update, and device monitoring. If a large number of tracing records are displayed, you can filter the records by service type, node name, and message status. If you need to further analyze the result data, you can export the data.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel