emqx/apps/emqx_bridge_mqtt
Kjell Winblad ef9884cf47 refactor(rule trace): templates rendered trace to increase code reuse
* The code for passing the trace context to a sub process has been
  improved to increase code reuse. This code is used when the action
  templates are rendered in a sub process.
* A macro has also been added for the error term that is thrown when the
  action shall be stopped after the templates has been rendered. This is
  also done to reduce code duplication and to reduce the risk of
  introducing bugs due to typos.
* Fix incorrect type spec

Thanks to @zmstone for suggesting these improvements in comments to a PR
(https://github.com/emqx/emqx/pull/12916).
2024-04-25 13:15:36 +02:00
..
src refactor(rule trace): templates rendered trace to increase code reuse 2024-04-25 13:15:36 +02:00
test chore: update copyright-year 2024-02-23 08:21:06 +01:00
README.md chore(mqttbridge): add README 2023-05-30 17:56:35 +03:00
rebar.config Merge remote-tracking branch 'upstream/release-54' into 0105-sync-r54 2024-01-05 14:20:38 +01:00

README.md

EMQX MQTT Broker Bridge

This application connects EMQX to virtually any MQTT broker adhering to either MQTTv3 or MQTTv5 standard. The connection is facilitated through the MQTT bridge abstraction, allowing for the flow of data in both directions: from the remote broker to EMQX (ingress) and from EMQX to the remote broker (egress).

User can create a rule and easily ingest into a remote MQTT broker by leveraging EMQX Rules.

Documentation

  • Refer to Bridge Data into MQTT Broker for how to use EMQX dashboard to set up ingress or egress bridge, or even both at the same time.

  • Refer to EMQX Rules for the EMQX rules engine introduction.

HTTP APIs

Several APIs are provided for bridge management, refer to API Docs - Bridges for more detailed information.

Contributing

Please see our contributing guide.

License

Apache License 2.0, see LICENSE.