docs: add info about that rule engine can handle different types of structured data
Co-authored-by: Zaiming (Stone) Shi <zmstone@gmail.com>
This commit is contained in:
parent
08e249dc4d
commit
89782e6d21
|
@ -14,8 +14,8 @@ specifying a topic filter and a set of conditions that need to be met. If a
|
|||
message matches the topic filter and all the conditions are met, the rule is
|
||||
triggered. The rule can then transform the message and route it to a different
|
||||
topic, or send it to another service (defined by an EMQX bridge). The rule
|
||||
engine's message data transformation is designed to work well with JSON
|
||||
formatted data.
|
||||
engine's message data transformation is designed to work well with structured data
|
||||
such as JSON, avro, and protobuf.
|
||||
|
||||
|
||||
A rule consists of the three parts **MATCH**, **TRANSFORM** and **ACTIONS** that are
|
||||
|
|
Loading…
Reference in New Issue