This topic describes how to create an event stream whose event provider is ApsaraMQ for MQTT in the EventBridge console.
Prerequisites
EventBridge is activated and the required permissions are granted to a Resource Access Management (RAM) user. For more information, see Activate EventBridge and grant permissions to a RAM user.
An ApsaraMQ for MQTT instance is created. Make sure that the instance is in the Running state. For more information, see Create resources.
Procedure
Log on to the EventBridge console. In the left-side navigation pane, click Event Streams.
In the top navigation bar, select a region and click Create Event Stream.
On the Create Event Stream page, configure the Task Name and Description parameters and follow the on-screen instructions to configure other parameters. Then, click Save. The following section describes the parameters:
Task Creation
In the Source step, set the Data Provider parameter to Message Queue for MQTT and follow the on-screen instructions to configure other parameters. Then, click Next Step. The following table describes the parameters.
Parameter
Description
Example
MQTT Instance
The ApsaraMQ for MQTT instance on which messages are produced.
test-instance
MQTT Topic
The topic in which messages are produced on the ApsaraMQ for MQTT instance.
test-topic
Batch Push
The batch push feature helps you aggregate multiple events at a time. This feature is triggered if the condition that is specified by the Messages parameter or the Batch Push Interval (Unit: Seconds) parameter is met.
For example, if you set the Messages parameter to 100 and the Interval (Unit: Seconds) parameter to 15, the push is executed when the number of messages reaches 100 even if only 10 seconds are elapsed.
Enable
Messages
The maximum number of messages that can be sent in each function invocation. Requests are sent only when the number of messages in the backlog reaches the specified value. Valid values: 1 to 10000.
100
Batch Push Interval (Unit: Seconds)
The time interval at which the function is invoked. The system sends the aggregated messages to Function Compute at the specified time interval. Valid values: 0 to 15. Unit: seconds. The value 0 indicates that messages are immediately sent after aggregation.
3
In the Filtering, Transformation, and Sink steps, configure the event filtering method, event transformation rule, and event target. For information about event transformation configurations, see Use Function Compute to perform message cleansing.
Task Property
Configure the retry policy and dead-letter queue for the event stream. For more information, see Retry policies and dead-letter queues.
Go back to the Event Streams page and find the event stream that you created. Then, click Enable in the Actions column.
Enabling an event stream requires 30 to 60 seconds to complete. You can view the progress in the Status column of the event stream on the Event Streams page.
Sample event
{
"specversion":"1.0",
"id":"AC1EC0C950650816F27D46F7D7CA****",
"source":"acs:mqtt",
"type":"mqtt:Topic:SendMessage",
"subject":"acs:mq:cn-hangzhou:143998900779****:topic/mqtt-cn-2r42qam****/housekee****",
"datacontenttype":"application/json; charset\u003dutf-8",
"time":"2022-06-22T03:53:47.959Z",
"aliyunaccountid":"143998900779****",
"data":{
"props":{
"firstTopic":"housekee****",
"secondTopic":"/testMq4****",
"clientId":"GID_****"
},
"body":"TEST"
}
}
For information about the parameters defined in the CloudEvents specification, see Overview.
The following table describes the parameters contained in data.
Parameter | Type | Example | Description |
props | Map | The message attributes. | |
firstTopic | String | housekee**** | The parent topic that is used to send and receive messages. |
secondTopic | String | /testMq4**** | The subtopic. |
clientId | String | GID_**** | The client ID. |
body | String | TEST | The message body. |