Reference
The reference guide is a detailed introduction to TDengine including various TDengine connectors in different languages, and the tools that come with TDengine.
๐๏ธ REST API
To support the development of various types of applications and platforms, TDengine provides an API that conforms to REST principles; namely REST API. To minimize the learning cost, unlike REST APIs for other database engines, TDengine allows insertion of SQL commands in the BODY of an HTTP POST request, to operate the database.
๐๏ธ connector
8 items
๐๏ธ taosAdapter
taosAdapter is a TDengine companion tool that acts as a bridge and adapter between TDengine clusters and applications. It provides an easy-to-use and efficient way to ingest data directly from data collection agent software such as Telegraf, StatsD, collectd, etc. It also provides an InfluxDB/OpenTSDB compatible data ingestion interface, allowing InfluxDB/OpenTSDB applications to be seamlessly ported to TDengine.
๐๏ธ taosBenchmark
taosBenchmark (once called taosdemo ) is a tool for testing the performance of TDengine.
๐๏ธ taosdump
taosdump is a tool that supports backing up data from a running TDengine cluster and restoring the backed up data to the same, or another running TDengine cluster.
๐๏ธ TDinsight
TDinsight is a solution for monitoring TDengine using the builtin native monitoring database and [Grafana].
๐๏ธ Command Line Interface
Instructions and tips for using the TDengine CLI
๐๏ธ supported platforms
List of platforms supported by TDengine server, client, and connector
๐๏ธ TDengine Docker images
This chapter describes how to start the TDengine service in a container and access it. Users can control the behavior of the service in the container by using environment variables on the docker run command-line or in the docker-compose file.
๐๏ธ Configuration
Configuration parameters for client and server in TDengine
๐๏ธ File directory structure
TDengine installation directory description
๐๏ธ Schemaless writing
The Schemaless write method eliminates the need to create super tables/sub tables in advance and automatically creates the storage structure corresponding to the data, as it is written to the interface.
