fix merge conflicts
sheyanjie-qq
|
|
@ -7,19 +7,19 @@ import Tabs from "@theme/Tabs";
|
|||
import TabItem from "@theme/TabItem";
|
||||
import Image from '@theme/IdealImage';
|
||||
import imgConnect from '../assets/connecting-to-tdengine-01.png';
|
||||
import ConnJava from "./_connect_java.mdx";
|
||||
import ConnGo from "./_connect_go.mdx";
|
||||
import ConnRust from "./_connect_rust.mdx";
|
||||
import ConnNode from "./_connect_node.mdx";
|
||||
import ConnPythonNative from "./_connect_python.mdx";
|
||||
import ConnCSNative from "./_connect_cs.mdx";
|
||||
import ConnC from "./_connect_c.mdx";
|
||||
import InstallOnLinux from "../14-reference/05-connector/_linux_install.mdx";
|
||||
import InstallOnWindows from "../14-reference/05-connector/_windows_install.mdx";
|
||||
import InstallOnMacOS from "../14-reference/05-connector/_macos_install.mdx";
|
||||
import VerifyLinux from "../14-reference/05-connector/_verify_linux.mdx";
|
||||
import VerifyMacOS from "../14-reference/05-connector/_verify_macos.mdx";
|
||||
import VerifyWindows from "../14-reference/05-connector/_verify_windows.mdx";
|
||||
import ConnJava from "../assets/resources/_connect_java.mdx";
|
||||
import ConnGo from "../assets/resources/_connect_go.mdx";
|
||||
import ConnRust from "../assets/resources/_connect_rust.mdx";
|
||||
import ConnNode from "../assets/resources/_connect_node.mdx";
|
||||
import ConnPythonNative from "../assets/resources/_connect_python.mdx";
|
||||
import ConnCSNative from "../assets/resources/_connect_cs.mdx";
|
||||
import ConnC from "../assets/resources/_connect_c.mdx";
|
||||
import InstallOnLinux from "../assets/resources/_linux_install.mdx";
|
||||
import InstallOnWindows from "../assets/resources/_windows_install.mdx";
|
||||
import InstallOnMacOS from "../assets/resources/_macos_install.mdx";
|
||||
import VerifyLinux from "../assets/resources/_verify_linux.mdx";
|
||||
import VerifyMacOS from "../assets/resources/_verify_macos.mdx";
|
||||
import VerifyWindows from "../assets/resources/_verify_windows.mdx";
|
||||
|
||||
TDengine provides a rich set of application development interfaces. To facilitate users in quickly developing their applications, TDengine supports connectors for multiple programming languages. The official connectors include support for C/C++, Java, Python, Go, Node.js, C#, Rust, Lua (community contribution), and PHP (community contribution). These connectors support connecting to the TDengine cluster using the native interface (taosc) and REST interface (not supported in some languages yet). Community developers have also contributed several unofficial connectors, such as ADO.NET connector, Lua connector, and PHP connector. Additionally, TDengine can directly call the REST API provided by taosadapter for data writing and querying operations.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Prometheus
|
|||
slug: /third-party-tools/data-collection/prometheus
|
||||
---
|
||||
|
||||
import Prometheus from "./_prometheus.mdx"
|
||||
import Prometheus from "../../assets/resources/_prometheus.mdx"
|
||||
|
||||
Prometheus is a popular open-source monitoring and alerting system. In 2016, Prometheus joined the Cloud Native Computing Foundation (CNCF), becoming the second hosted project after Kubernetes. The project has a very active developer and user community.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Telegraf
|
|||
slug: /third-party-tools/data-collection/telegraf
|
||||
---
|
||||
|
||||
import Telegraf from "./_telegraf.mdx"
|
||||
import Telegraf from "../../assets/resources/_telegraf.mdx"
|
||||
|
||||
Telegraf is a very popular open-source metric collection software. In data collection and platform monitoring systems, Telegraf can collect operational information from various components without the need to manually write scripts for periodic collection, reducing the difficulty of data acquisition.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: collectd
|
|||
slug: /third-party-tools/data-collection/collectd
|
||||
---
|
||||
|
||||
import CollectD from "./_collectd.mdx"
|
||||
import CollectD from "../../assets/resources/_collectd.mdx"
|
||||
|
||||
collectd is a daemon for collecting system performance. collectd provides various storage mechanisms to store different values. It periodically collects relevant statistical information about the system while it is running and storing information. Utilizing this information helps identify current system performance bottlenecks and predict future system loads.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: StatsD
|
|||
slug: /third-party-tools/data-collection/statsd
|
||||
---
|
||||
|
||||
import StatsD from "./_statsd.mdx"
|
||||
import StatsD from "../../assets/resources/_statsd.mdx"
|
||||
|
||||
StatsD is a simple daemon for aggregating and summarizing application metrics that has rapidly evolved in recent years into a unified protocol for collecting application performance metrics.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Icinga2
|
|||
slug: /third-party-tools/data-collection/icinga2
|
||||
---
|
||||
|
||||
import Icinga2 from "./_icinga2.mdx"
|
||||
import Icinga2 from "../../assets/resources/_icinga2.mdx"
|
||||
|
||||
icinga2 is an open-source host and network monitoring software, originally developed from the Nagios network monitoring application. Currently, icinga2 is released under the GNU GPL v2 license.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: TCollector
|
|||
slug: /third-party-tools/data-collection/tcollector
|
||||
---
|
||||
|
||||
import TCollector from "./_tcollector.mdx"
|
||||
import TCollector from "../../assets/resources/_tcollector.mdx"
|
||||
|
||||
TCollector is part of openTSDB, used for collecting client logs and sending them to the database.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,11 +6,11 @@ slug: /tdengine-reference/components/taosadapter
|
|||
|
||||
import Image from '@theme/IdealImage';
|
||||
import imgAdapter from '../../assets/taosadapter-01.png';
|
||||
import Prometheus from "../../10-third-party/01-collection/_prometheus.mdx"
|
||||
import CollectD from "../../10-third-party/01-collection/_collectd.mdx"
|
||||
import StatsD from "../../10-third-party/01-collection/_statsd.mdx"
|
||||
import Icinga2 from "../../10-third-party/01-collection/_icinga2.mdx"
|
||||
import TCollector from "../../10-third-party/01-collection/_tcollector.mdx"
|
||||
import Prometheus from "../../assets/resources/_prometheus.mdx"
|
||||
import CollectD from "../../assets/resources/_collectd.mdx"
|
||||
import StatsD from "../../assets/resources/_statsd.mdx"
|
||||
import Icinga2 from "../../assets/resources/_icinga2.mdx"
|
||||
import TCollector from "../../assets/resources/_tcollector.mdx"
|
||||
|
||||
taosAdapter is a companion tool for TDengine, serving as a bridge and adapter between the TDengine cluster and applications. It provides an easy and efficient way to ingest data directly from data collection agents (such as Telegraf, StatsD, collectd, etc.). It also offers InfluxDB/OpenTSDB compatible data ingestion interfaces, allowing InfluxDB/OpenTSDB applications to be seamlessly ported to TDengine.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: /tdengine-reference/client-libraries/java
|
|||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
import RequestId from "./_request_id.mdx";
|
||||
import RequestId from "../../assets/resources/_request_id.mdx";
|
||||
|
||||
`taos-jdbcdriver` is the official Java connector for TDengine, allowing Java developers to develop applications that access the TDengine database. `taos-jdbcdriver` implements the interfaces of the JDBC driver standard.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: /tdengine-reference/client-libraries/go
|
|||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
import RequestId from "./_request_id.mdx";
|
||||
import RequestId from "../../assets/resources/_request_id.mdx";
|
||||
|
||||
`driver-go` is the official Go language connector for TDengine, implementing the interface of the Go language [database/sql](https://golang.org/pkg/database/sql/) package. Go developers can use it to develop applications that access data in the TDengine cluster.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,8 +7,8 @@ slug: /tdengine-reference/client-libraries/rust
|
|||
import Tabs from "@theme/Tabs";
|
||||
import TabItem from "@theme/TabItem";
|
||||
|
||||
import Preparation from "./_preparation.mdx";
|
||||
import RequestId from "./_request_id.mdx";
|
||||
import Preparation from "../../assets/resources/_preparation.mdx"
|
||||
import RequestId from "../../assets/resources/_request_id.mdx";
|
||||
|
||||
[](https://crates.io/crates/taos)  [](https://docs.rs/taos)
|
||||
|
||||
|
|
@ -27,17 +27,17 @@ Supports Rust 1.70 and above.
|
|||
|
||||
## Version History
|
||||
|
||||
| Rust Connector Version | Major Changes | TDengine Version |
|
||||
| -------------------- | --------------------------------------------------------------------------------------------------- | --------------- |
|
||||
| v0.12.3 | 1. Optimized WebSocket query and insert performance. <br/> 2. Supported VARBINARY and GEOMETRY types. | 3.3.0.0 and higher |
|
||||
| v0.12.0 | WebSocket supports compression. | 3.2.3.0 and higher |
|
||||
| v0.11.0 | TMQ feature optimization. | 3.2.0.0 and higher |
|
||||
| v0.10.0 | WebSocket endpoint change. | 3.1.0.0 and higher |
|
||||
| v0.9.2 | STMT: WebSocket to get tag_fields, col_fields. | 3.0.7.0 and higher |
|
||||
| v0.8.12 | Message subscription: get consumption progress and start consuming at a specified progress. | 3.0.5.0 and higher |
|
||||
| v0.8.0 | Supports schema-less writing. | 3.0.4.0 and higher |
|
||||
| v0.7.6 | Supports using req_id in requests. | 3.0.3.0 and higher |
|
||||
| v0.6.0 | Basic functionality. | 3.0.0.0 and higher |
|
||||
| Rust Connector Version | Major Changes | TDengine Version |
|
||||
| ---------------------- | ----------------------------------------------------------------------------------------------------- | ------------------ |
|
||||
| v0.12.3 | 1. Optimized WebSocket query and insert performance. <br/> 2. Supported VARBINARY and GEOMETRY types. | 3.3.0.0 and higher |
|
||||
| v0.12.0 | WebSocket supports compression. | 3.2.3.0 and higher |
|
||||
| v0.11.0 | TMQ feature optimization. | 3.2.0.0 and higher |
|
||||
| v0.10.0 | WebSocket endpoint change. | 3.1.0.0 and higher |
|
||||
| v0.9.2 | STMT: WebSocket to get tag_fields, col_fields. | 3.0.7.0 and higher |
|
||||
| v0.8.12 | Message subscription: get consumption progress and start consuming at a specified progress. | 3.0.5.0 and higher |
|
||||
| v0.8.0 | Supports schema-less writing. | 3.0.4.0 and higher |
|
||||
| v0.7.6 | Supports using req_id in requests. | 3.0.3.0 and higher |
|
||||
| v0.6.0 | Basic functionality. | 3.0.0.0 and higher |
|
||||
|
||||
## Exceptions and Error Codes
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: /tdengine-reference/client-libraries/python
|
|||
|
||||
import Tabs from "@theme/Tabs";
|
||||
import TabItem from "@theme/TabItem";
|
||||
import RequestId from "./_request_id.mdx";
|
||||
import RequestId from "../../assets/resources/_request_id.mdx";
|
||||
|
||||
`taopsy` is the official connector provided by TDengine database for Python language, which provides multiple access interfaces for database writing, querying, subscribing, etc.
|
||||
|
||||
|
|
@ -145,7 +145,7 @@ Example program source code can be found at:
|
|||
## About Nanosecond (nanosecond)
|
||||
|
||||
Due to the current imperfect support for nanoseconds in Python (see the links below), the current implementation returns an integer when nanosecond precision is used, rather than the datetime type returned for ms and us. Application developers need to handle this themselves, and it is recommended to use pandas' to_datetime(). If Python officially fully supports nanoseconds in the future, the Python connector may modify the relevant interfaces.
|
||||
|
||||
|
||||
## Common Questions
|
||||
|
||||
Feel free to [ask questions or report issues](https://github.com/taosdata/taos-connector-python/issues).
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: /tdengine-reference/client-libraries/node
|
|||
|
||||
import Tabs from "@theme/Tabs";
|
||||
import TabItem from "@theme/TabItem";
|
||||
import RequestId from "./_request_id.mdx";
|
||||
import RequestId from "../../assets/resources/_request_id.mdx";
|
||||
|
||||
`@tdengine/websocket` is the official Node.js language connector for TDengine. Node.js developers can use it to develop applications that access the TDengine database.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: /tdengine-reference/client-libraries/csharp
|
|||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
import RequestId from "./_request_id.mdx";
|
||||
import RequestId from "../../assets/resources/_request_id.mdx";
|
||||
|
||||
`TDengine.Connector` is the C# language connector provided by TDengine. C# developers can use it to develop C# applications that access data in the TDengine cluster.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: /tdengine-reference/client-libraries/r-lang
|
|||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
import Rdemo from "../../07-develop/_connect_r.mdx"
|
||||
import Rdemo from "../../assets/resources/_connect_r.mdx"
|
||||
|
||||
The RJDBC library in R language can enable R language programs to access TDengine data. Here are the installation process, configuration process, and R language example code.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,12 +7,12 @@ import Tabs from "@theme/Tabs";
|
|||
import TabItem from "@theme/TabItem";
|
||||
import Image from '@theme/IdealImage';
|
||||
import imgClientLib from '../../assets/client-libraries-01.png';
|
||||
import InstallOnLinux from "./_linux_install.mdx";
|
||||
import InstallOnWindows from "./_windows_install.mdx";
|
||||
import InstallOnMacOS from "./_macos_install.mdx";
|
||||
import VerifyWindows from "./_verify_windows.mdx";
|
||||
import VerifyLinux from "./_verify_linux.mdx";
|
||||
import VerifyMacOS from "./_verify_macos.mdx";
|
||||
import InstallOnLinux from "../../assets/resources/_linux_install.mdx";
|
||||
import InstallOnWindows from "../../assets/resources/_windows_install.mdx";
|
||||
import InstallOnMacOS from "../../assets/resources/_macos_install.mdx";
|
||||
import VerifyWindows from "../../assets/resources/_verify_windows.mdx";
|
||||
import VerifyLinux from "../../assets/resources/_verify_linux.mdx";
|
||||
import VerifyMacOS from "../../assets/resources/_verify_macos.mdx";
|
||||
|
||||
TDengine provides a rich set of application development interfaces. To facilitate users in quickly developing their own applications, TDengine supports connectors for multiple programming languages, including official connectors for C/C++, Java, Python, Go, Node.js, C#, and Rust. These connectors support connecting to the TDengine cluster using the native interface (taosc) and WebSocket interface. Community developers have also contributed several unofficial connectors, such as the ADO.NET connector, Lua connector, and PHP connector.
|
||||
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 179 KiB After Width: | Height: | Size: 125 KiB |
|
Before Width: | Height: | Size: 117 KiB After Width: | Height: | Size: 132 KiB |
|
Before Width: | Height: | Size: 133 KiB After Width: | Height: | Size: 79 KiB |
|
Before Width: | Height: | Size: 105 KiB After Width: | Height: | Size: 66 KiB |
|
Before Width: | Height: | Size: 48 KiB After Width: | Height: | Size: 264 KiB |
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 82 KiB |
|
Before Width: | Height: | Size: 96 KiB After Width: | Height: | Size: 51 KiB |
|
Before Width: | Height: | Size: 133 KiB After Width: | Height: | Size: 87 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 163 KiB After Width: | Height: | Size: 98 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 88 KiB |
|
Before Width: | Height: | Size: 282 KiB After Width: | Height: | Size: 159 KiB |
|
Before Width: | Height: | Size: 75 KiB After Width: | Height: | Size: 105 KiB |
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 47 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 148 KiB |
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 152 KiB |
|
Before Width: | Height: | Size: 103 KiB After Width: | Height: | Size: 244 KiB |
|
Before Width: | Height: | Size: 194 KiB After Width: | Height: | Size: 203 KiB |
|
Before Width: | Height: | Size: 106 KiB After Width: | Height: | Size: 60 KiB |
|
Before Width: | Height: | Size: 155 KiB After Width: | Height: | Size: 130 KiB |
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 127 KiB |
|
Before Width: | Height: | Size: 27 KiB After Width: | Height: | Size: 139 KiB |
|
|
@ -276,11 +276,11 @@ TDinsight插件中展示的数据是通过taosKeeper和taosAdapter服务收集
|
|||
|
||||
### 30 为什么开源版 TDengine 的主进程会建立一个与公网的连接？
|
||||
这个连接只会上报不涉及任何用户数据的最基本信息，用于官方了解产品在世界范围内的分布情况，进而优化产品，提升用户体验，具体采集项目为：集群名、操作系统版本、cpu信息等。
|
||||
该特性为可选配置项，在开源版中默认开启，具体参数为 telemetryReporting , 在官方文档中有做说明，链接如下：
|
||||
https://docs.taosdata.com/reference/components/taosd/#%E7%9B%91%E6%8E%A7%E7%9B%B8%E5%85%B3
|
||||
该特性为可选配置项，在开源版中默认开启，具体参数为 telemetryReporting , 在官方文档中有做说明，链接如下：[参数简介](https://docs.taosdata.com/reference/components/taosd/#%E7%9B%91%E6%8E%A7%E7%9B%B8%E5%85%B3)
|
||||
您可以随时关闭该参数，只需要在taos.cfg 中修改telemetryReporting为 0，然后重启数据库服务即可。
|
||||
代码位于:https://github.com/taosdata/TDengine/blob/62e609c558deb764a37d1a01ba84bc35115a85a4/source/dnode/mnode/impl/src/mndTelem.c
|
||||
此外，对于安全性要求极高的企业版 TDengine Enterprise 来说，此参数不会工作。
|
||||
代码位于:[点击此处](https://github.com/taosdata/TDengine/blob/62e609c558deb764a37d1a01ba84bc35115a85a4/source/dnode/mnode/impl/src/mndTelem.c)
|
||||
此外，对于安全性要求极高的企业版 TDengine Enterprise 来说，此参数不会工作。
|
||||
|
||||
### 31 第一次连接集群时遇到“Sync leader is unreachable”怎么办？
|
||||
报这个错，说明第一次向集群的连接是成功的，但第一次访问的IP不是mnode的leader节点，客户端试图与leader建立连接时发生错误。客户端通过EP，也就是指定的fqdn与端口号寻找leader节点，常见的报错原因有两个：
|
||||
|
||||
|
|
@ -297,4 +297,4 @@ https://docs.taosdata.com/reference/components/taosd/#%E7%9B%91%E6%8E%A7%E7%9B%B
|
|||
|
||||
问题影响：服务器重启后，原有数据库丢失（注：并非真正丢失，只是原有的数据磁盘未挂载，暂时看不到）且集群 ID 发生变化，导致无法访问原有数据库。对于企业版用户，如果已针对集群 ID 进行授权，还会发现集群服务器的机器码未变，但原有的授权已失效。如果未针对该问题进行监控或者未及时发现并进行处理，则用户不会注意到原有数据库已经丢失，从而造成损失，增加运维成本。
|
||||
|
||||
问题解决：应在 fstab 文件中配置 dataDir 目录的自动挂载，确保 dataDir 始终指向预期的挂载点和目录，此时，再重启服务器，会找回原有的数据库和集群。在后续的版本中，我们将开发一个功能，使 taosd 在检测到启动前后 dataDir 发生变化时，在启动阶段退出，同时提供相应的错误提示。
|
||||
问题解决：应在 fstab 文件中配置 dataDir 目录的自动挂载，确保 dataDir 始终指向预期的挂载点和目录，此时，再重启服务器，会找回原有的数据库和集群。在后续的版本中，我们将开发一个功能，使 taosd 在检测到启动前后 dataDir 发生变化时，在启动阶段退出，同时提供相应的错误提示。
|
||||
|
|
|
|||