From 89782e6d2113e794b6931e5e4d75c9d3d15a46e2 Mon Sep 17 00:00:00 2001 From: Kjell Winblad Date: Tue, 21 Mar 2023 06:26:04 +0100 Subject: [PATCH] docs: add info about that rule engine can handle different types of structured data Co-authored-by: Zaiming (Stone) Shi --- apps/emqx_rule_engine/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/emqx_rule_engine/README.md b/apps/emqx_rule_engine/README.md index f1533a0e3..2c2e43db3 100644 --- a/apps/emqx_rule_engine/README.md +++ b/apps/emqx_rule_engine/README.md @@ -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