![]() some telemetry events from wolff are discarded: * dropped: this is double counted in wolff, we now only subscribe to the dropped_queue_full event * retried_failed: it has different meanings in wolff, in wolff, it means it's the 2nd (or onward) produce attempt in EMQX, it means it's eventually failed after some retries * retried_success since we are going to handle the success counters in callbac this having this reported from wolff will only make things harder to understand * failed wolff never fails (unelss drop which is a different counter) |
||
---|---|---|
.. | ||
etc | ||
i18n | ||
include | ||
src | ||
test | ||
.gitignore | ||
README.md | ||
rebar.config |
README.md
emqx_bridge
EMQX Data Bridge is an application that managing the resources (see emqx_resource) used by emqx rule engine.
It provides CRUD HTTP APIs of the resources, and is also responsible for loading the resources at
startup, and saving configs of resources to data/
after configs updated.
The application depends on emqx_connector
as that's where all the callback modules of connector
resources placed.