Formats in which dumped logs are printed

Updated at: 2023-10-07 01:58

When you dump an IoT Platform log, the format in which the log is printed varies based on the business type of the log. This topic describes the formats in which logs of each business type are printed and the corresponding parameters.

Background information

Formats

Business type

bizCode

Format

Business type

bizCode

Format

Device behaviors

device

time||traceId||utcTime||messageId||instanceId||uid||productKey||deviceName||bizCode||operation||status||code||reason||content||requestId||password||sourceIp||protocol||transport||clientId||authType||size||deviceFingerprint

Devices send messages to IoT Platform.

uplink

time||traceId||utcTime||uid||bizCode||operation||messageId||productKey||deviceName||code||status||reason||content||instanceId||requestId||connectionId||params||resultData

Downstream messages

downlink

Topic subscription

subscribe

Topic unsubscription

unsubscribe

Server-side subscription

ServerSubscribe

Rules engine (data forwarding)

ruleengine

time||traceId||productKey||deviceName||iotId||uid||messageId||code||reason||status||params||resultData||bizCode||operation||tenantId||content||requestId||instanceId||utcTime||dtInstanceId

TSL models (TSL data verification, TSL service calls, and TSL messages)

ThingModel

time||tenantId||traceId||instanceId||bizCode||operation||productKey||deviceName||iotId||status||code||messageId||reason||params||resultData||uid||utcTime||bizType||requestId

Hot data storage

HotDataStorage

Message parsing

ScriptParsing

API calls

ApiService

time||traceId||requestId||uid||tenantId||instanceId||productKey||deviceName||iotId||messageId||code||status||reason||bizCode||operation||params||resultData||utcTime

Device shadows

DeviceShadow

time||traceId||utcTime||uid||bizCode||operation||messageId||productKey||deviceName||code||reason||content||instanceId||status||requestId||connectionId

OTA updates

OTA

time||tenantId||traceId||instanceId||bizCode||operation||productKey||deviceName||iotId||status||code||messageId||reason||params||resultData||uid||utcTime

Topological relationships

ThingTopo

Remote configuration

RemoteConfig

Device jobs

ThingJob

Others

Other

IoT Twin Engine

DigitalTwin

time||tenantId||traceId||instanceId||bizCode||operation||productKey||deviceName||iotId||status||code||messageId||reason||params||resultData||uid||utcTime||dtInstanceId

Parameters

Parameter

Description

Parameter

Description

requestId

The ID of the request.

time

The time when the log was printed.

utcTime

The time when the log was printed. The time follows the ISO 8601 standard in the yyyy-MM-ddThh:mm:ssZ format. The time is displayed in UTC.

traceId

The trace ID. You can use the ID to trace the destinations to which the message was forwarded.

messageId

The ID of the message.

instanceId

The ID of the instance.

uid

The ID of the Alibaba Cloud account.

productKey

The ProductKey of the product.

deviceName

The DeviceName of the device.

bizCode

The business type.

operation

The name of the operation, the name of the API operation, the method of the service, or the topic of the message, which corresponds to the business type.

For more information about operation names, see Log fields. For more information about API operation names, see List of operations by function. For more information about service methods and message topics, see Alink protocol.

status

The status of the operation. Valid values:

  • true: The operation is successful.

  • false: The operation failed.

code

The error code returned For more information, see IoT Platform logs.

reason

The cause of the error.

content

The content of the log.

password

The DeviceSecret that you specified when you connected the device.

sourceIp

The IP address of the device.

protocol

The communication protocol. Valid values:

  • mqtt: Message Queuing Telemetry Transport (MQTT)

  • mqtt-over-websocket: MQTT over WebSocket connections

transport

The transmission protocol. Example: TLS 1.2 and TLS 1.3.

clientId

The ID of the client.

authType

The verification method.

size

The size of the message content.

deviceFingerprint

The device fingerprint.

connectionId

The ID of the connection.

params

The details of the message parameters.

resultData

The execution result.

dtInstanceId

The ID of the twin space.

  • On this page (1, T)
  • Background information
  • Formats
  • Parameters
Feedback
phone Contact Us

Chat now with Alibaba Cloud Customer Service to assist you in finding the right products and services to meet your needs.

alicare alicarealicarealicare