IoT Platform:View logs

Device logs

You can view the execution results on the device.

• Connection logs:

  The following log indicates that the device successfully connected to the IoT Platform.

  [1578054042.600][LK-0313] MQTT user calls aiot_mqtt_connect api, connect
  [1578054042.600][LK-0317] LightSwitch&a18wP******
  [1578054042.600][LK-0318] 24FEB95E42CADB18D0E093F412E6AC27705AA8DF6DB3B649566728E685******
  [1578054042.600][LK-0319] a18wP******.LightSwitch|timestamp=2524608000000，_ss=1,_v=sdk-c-4.0.0,securemode=2,signmethod=hmacsha256,ext=1,|
  establish mbedtls connection with server(host='a18wP******.iot-as-mqtt.cn-shanghai.aliyuncs.com', port=[1883])
  success to establish mbedtls connection, fd = 3
  [1578054042.711][LK-0313] MQTT connect success
  AIOT_MQTTEVT_CONNECT

• Received message log:

  After you call the RRPC API operation to send a request with the payload ping to a custom topic such as /a18wP******/LightSwitch/user/get, the device receives the message and prints the following log.

  • Log details:

    [1578054379.700][LK-0309] pub: /ext/rrpc/1213074107617******/a18wP******/LightSwitch/user/get
    [LK-030A] < 70 69 6E 67                                      | ping
    pub, qos: 0, topic: 1213074107617******/a18wP******/LightSwitch/user/get
    pub, payload: ping

  • Log description:

    In this log, /ext/rrpc/1213074107617******/a18wP******/LightSwitch/user/get is the RRPC request topic, 1213074107617****** is the message ID, and ping is the message payload. For more information, see Call a custom topic (Recommended).

• Response log:

  After the device receives the RRPC message, it sends a response and prints the following log.

  [1578054379.700][LK-0309] pub: /ext/rrpc/1213074107617******/a18wP******/LightSwitch/user/get
  [LK-030A] > 70 6F 6E 67                                      | pong

IoT Platform logs

Log in to the IoT Platform console. In the left-side navigation pane, choose Monitoring and O&M > Simple Log Service, and then select a product to view the communication logs for your device.

The page contains four tabs: cloud log, device local log, message trace, and log dump. On the cloud log tab, you can filter logs by DeviceName, TraceId, or Content Keyword/MessageId. The log list displays columns such as Time, TraceId, DeviceName, Business Type, Operation, Content, and Status. For example, a log entry with Business Type set to API Call and Operation set to RRPC shows a status code of 200 when the call succeeds.