emqx/apps/emqx_bridge_mqtt
Kjell Winblad 9dc3a169b3 feat: split bridges into a connector part and a bridge part
Co-authored-by: Thales Macedo Garitezi <thalesmg@gmail.com>
Co-authored-by: Stefan Strigler <stefan.strigler@emqx.io>
Co-authored-by: Zaiming (Stone) Shi <zmstone@gmail.com>

Several bridges should be able to share a connector pool defined by a
single connector. The connectors should be possible to enable and
disable similar to how one can disable and enable bridges. There should
also be an API for checking the status of a connector and for
add/edit/delete connectors similar to the current bridge API.

Issues:
https://emqx.atlassian.net/browse/EMQX-10805
2023-10-30 14:48:47 +01:00
..
src chore(hooks): validate hookpoints and document hook callbacks 2023-09-26 14:27:42 +03:00
test feat: split bridges into a connector part and a bridge part 2023-10-30 14:48:47 +01:00
README.md chore(mqttbridge): add README 2023-05-30 17:56:35 +03:00
rebar.config fix(mqttbridge): ensure elixir release assembles successfully 2023-05-30 17:56:35 +03: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.