ef9884cf47
* 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). |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| BSL.txt | ||
| README.md | ||
| docker-ct | ||
| rebar.config | ||
README.md
EMQX TDEngine Bridge
TDEngine is an open-source, cloud-native time series database (TSDB) optimized for Internet of Things (IoT), Connected Cars, and Industrial IoT. It enables efficient, real-time ingestion, processing, and monitoring of petabytes of data per day, generated by billions of sensors and data collectors.
The application is used to connect EMQX and TDEngine. User can create a rule and easily ingest IoT data into TDEngine by leveraging EMQX Rules.
Documentation
-
Refer to Ingest Data into TDEngine for how to use EMQX dashboard to ingest IoT data into TDEngine.
-
Refer to EMQX Rules for the EMQX rules engine introduction.
HTTP APIs
-
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.
Contributing
Please see our contributing.md.
License
EMQ Business Source License 1.1, refer to LICENSE.