Docs

Cloud Native Message Engine

Best practices

Device status reporting to Kafka

In MQTT scenarios, device status reporting is a very common use case. After device information is reported to the MQTT server, the MQTT server needs to save all MQTT messages for subsequent analysis. This topic uses Kafka to implement device information reporting.

Scenario description

The device reports shadow information to the MQTT topic corresponding to its device ID.

The MQTT server is configured with rules to forward multiple eligible MQTT topics to a single Kafka topic.

Preparations

Install the MQTTX client, referring to the MQTTX official installation documentation.

Create a Cloud Native Message Engine MQTT instance with the specification mqtt.2k. For detailed operations, see Create MQTT Instance.

Create a Message Queue for Kafka instance, version 2.8.2. For detailed operations, see Create Instance.

Operation steps

In the Message Queue for Kafka console, create the target topic.

For detailed operations, see Create Topic, and create a topic named agg. In the instance details, obtain the VPC endpoint information for the SASL_PLAINTEXT access point, such as kafka-xxxxxxxxxxxxxxx.kafka.ivolces.com:9093.

In the Message Queue for Kafka console, create a Kafka user and configure the username, password, and permissions.

For detailed operations, see Create SASL User.

In the Cloud Native Message Engine MQTT Dashboard, create a Kafka producer connector.

For detailed operations, see Create Kafka Producer Connector.

In the host list, configure the PLAINTEXT endpoint address

Configure username and password

Select plain as the authentication method

In the Cloud Native Message Engine MQTT Dashboard, configure rule data input.

For detailed operations, see Create Rule.

The MQTT server rule matches all topics under device/#

Forward to the agg topic in Kafka

In the Cloud Native Message Engine MQTT Dashboard, configure rule action output.

Select the registered Kafka connector

Enter the Kafka topic name of the target endpoint

Result verification

Use the MQTTX client to simulate two devices and send data to the public endpoint of the MQTT instance.

id00125 sends a message to device/id00125

id00128 sends a message to device/id00128

Verify that the message has been matched in EMQX.

In the Message Queue for Kafka instance, verify that forwarded data is present in the agg topic.

Last updated: 2026.01.26 16:22:55