![]() This commit adds a rule engine configuration option for changing the implementation module used for the rule engine function jq. The two options are `jq_port` (uses Erlang port programs to interact with jq) and `jq_nif` (uses an Erlang NIF library to interact with jq). Thanks to @terry-xiaoyu (Xinyu Liu <506895667@qq.com>) for Chinese translations |
||
---|---|---|
.. | ||
etc | ||
i18n | ||
include | ||
src | ||
test | ||
.gitignore | ||
README.md | ||
rebar.config |
README.md
emqx-rule-engine
IoT Rule Engine
Concept
iot rule "Rule Name"
when
match TopicFilters and Conditions
select
para1 = val1
para2 = val2
then
take action(#{para2 => val1, #para2 => val2})
Architecture
|-----------------|
Pub ---->| Message Routing |----> Sub
|-----------------|
| /|\
\|/ |
|-----------------|
| Rule Engine |
|-----------------|
| |
Backends Services Bridges
SQL for Rule query statement
select id, time, temperature as t from "topic/a" where t > 50;