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 APITo 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.

🗃️ connector8 items

📄️ taosAdaptertaosAdapter 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.

📄️ taosBenchmarktaosBenchmark (once called taosdemo ) is a tool for testing the performance of TDengine.

📄️ taosdumptaosdump 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.

📄️ TDinsightTDinsight is a solution for monitoring TDengine using the builtin native monitoring database and [Grafana].

📄️ Command Line InterfaceInstructions and tips for using the TDengine CLI

📄️ supported platformsList of platforms supported by TDengine server, client, and connector

📄️ TDengine Docker imagesThis 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.

📄️ ConfigurationConfiguration parameters for client and server in TDengine

📄️ File directory structureTDengine installation directory description

📄️ Schemaless writingThe 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.