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 |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| README.md | ||
| rebar.config | ||
EMQX HTTP Broker Bridge
This application enables EMQX to connect to any HTTP API, conforming to the HTTP standard. The connection is established via the HTTP bridge abstraction, which facilitates the unidirectional flow of data from EMQX to the HTTP API (egress).
Users can define a rule and efficiently transfer data to a remote HTTP API utilizing EMQX Rules.
Documentation
-
For instructions on how to use the EMQX dashboard to set up an egress bridge, refer to Bridge Data into HTTP API.
-
To understand the EMQX rules engine, please refer to EMQX Rules.
HTTP APIs
We provide a range of APIs for bridge management. For more detailed information, refer to API Docs -Bridges.
Contributing
For those interested in contributing, please consult our contributing guide.
License
This software is under the Apache License 2.0. For more details, see LICENSE.