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	chore: update copyright-year	2024-02-23 08:21:06 +01:00
BSL.txt	chore: update BSL license change date	2024-01-29 16:47:31 +01:00
README.md	docs: fix invalid links	2023-05-15 11:18:09 +08:00
docker-ct	refactor: redis bridge to its own application	2023-06-27 10:24:44 +02:00
rebar.config	style: erlfmt all `rebar.config` files and `bin/nodetool`	2023-12-29 09:08:03 +08:00

EMQX Redis Bridge

Redis is an in-memory data structure store, used as a distributed, in-memory key–value database, cache and message broker, with optional durability.

The application is used to connect EMQX and Redis. User can create a rule and easily ingest IoT data into Redis by leveraging EMQX Rules.

Documentation

Refer to Ingest Data into Redis for how to use EMQX dashboard to ingest IoT data into Redis.
Refer to EMQX Rules for the EMQX rules engine introduction.

Several APIs are provided for bridge management, which includes create bridge, update bridge, get bridge, stop or restart bridge and list bridges etc.

Refer to API Docs - Bridges for more detailed information.

Please see our contributing.md.

EMQ Business Source License 1.1, refer to LICENSE.