History

Kjell Winblad 5bfe31b691 fix: issues found during PR review (thanks @thalesmg and @zmstone) * Simpler handling of true and false in best effort JSON formatter * inet:ntoa/1 to format IP addresses * Made a record for lazy formatted trace values and formatter to improve maintainability * Added callback to format return value from connector * Extended test case to check that the format return value callback works * Added handling of "lazy" trace entry data to the text formatter. Do we need to handle this data in the normal log formatters as well?		2024-05-03 15:04:57 +02:00
..
src	fix: issues found during PR review (thanks @thalesmg and @zmstone)	2024-05-03 15:04:57 +02:00
test	fix(http connector): deobfuscate sensitive headers	2024-04-29 15:20:46 -03:00
README.md	refactor: HTTP connector into emqx_bridge_http app	2023-07-12 14:46:43 +02:00
rebar.config	style: erlfmt all `rebar.config` files and `bin/nodetool`	2023-12-29 09:08:03 +08:00

README.md

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.