This is an automated email from the ASF dual-hosted git repository.
zhaoqingran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hertzbeat.git
The following commit(s) were added to refs/heads/master by this push:
new 997bbe39c [doc] Add help document for tidb and nacos monitoring (#1823)
997bbe39c is described below
commit 997bbe39c098c6c3dfd50429129e00e136ca9038
Author: Alan <[email protected]>
AuthorDate: Tue Apr 23 21:24:42 2024 +0800
[doc] Add help document for tidb and nacos monitoring (#1823)
Signed-off-by: Alan <[email protected]>
Signed-off-by: Logic <[email protected]>
Co-authored-by: Logic <[email protected]>
---
home/docs/help/guide.md | 2 +
home/docs/help/nacos.md | 93 ++++++++++++++++++++++
home/docs/help/tidb.md | 55 +++++++++++++
.../current/help/guide.md | 2 +
.../current/help/nacos.md | 93 ++++++++++++++++++++++
.../current/help/tidb.md | 49 ++++++++++++
home/sidebars.json | 11 ++-
manager/src/main/resources/define/app-tidb.yml | 2 +-
8 files changed, 303 insertions(+), 4 deletions(-)
diff --git a/home/docs/help/guide.md b/home/docs/help/guide.md
index 8349dfde8..1783e0487 100644
--- a/home/docs/help/guide.md
+++ b/home/docs/help/guide.md
@@ -35,6 +35,7 @@ sidebar_label: Help Center
 👉 [DM database monitoring](dm) <br />
 👉 [OpenGauss database monitoring](opengauss) <br />
 👉 [IoTDB database monitoring](iotdb) <br />
+ 👉 [TiDB database monitoring](tidb) <br />
### Operating system monitoring
@@ -53,6 +54,7 @@ sidebar_label: Help Center
 👉 [RabbitMQ](rabbitmq) <br />
 👉 [ActiveMQ](activemq) <br />
 👉 [Jetty](jetty) <br />
+ 👉 [Nacos](nacos) <br />
### CloudNative monitoring
diff --git a/home/docs/help/nacos.md b/home/docs/help/nacos.md
new file mode 100644
index 000000000..1dbc4113c
--- /dev/null
+++ b/home/docs/help/nacos.md
@@ -0,0 +1,93 @@
+---
+id: nacos
+title: Monitoring：Nacos Server monitoring
+sidebar_label: Nacos Server
+keywords: [open source monitoring tool, open source middleware monitoring
tool, monitoring Nacos Server metrics]
+---
+
+> Hertzbeat monitors metrics of the Nacos Server by calling the Nacos Metrics
Api.
+
+### PreRequisites
+
+#### Deploy Nacos cluster to expose metrics data
+
+1. Deploy the Nacos cluster according to [deployment
document](https://nacos.io/en-us/docs/deployment.html).
+2. Configure the application. properties file to expose metrics data.
+```
+management.endpoints.web.exposure.include=*
+```
+3. Access ```{ip}:8848/nacos/actuator/prometheus``` to see if metrics data can
be accessed.
+
+More information see [Nacos monitor
guide](https://nacos.io/en-us/docs/monitor-guide.html).
+
+### Configuration parameter
+
+| Parameter name | Parameter help description
|
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Target Host | Monitored IPV4, IPV6 or domain name. Note⚠️Without
protocol header (eg: https://, http://)
|
+| Target name | Identify the name of this monitoring. The name needs to be
unique
|
+| Nacos Port | Port provided by the Nacos Server. The default
is 8848
|
+| Collection interval | Interval time of monitor periodic data collection,
unit: second, and the minimum interval that can be set is 30 seconds
|
+| Description remarks | For more information about identifying and describing
this monitoring, users can note information here
|
+
+### Collection Metric
+
+#### Metric set：jvm
+
+| Metric name | Metric unit | Metric help description |
+| ----------- | ----------- | ----------- |
+| system_cpu_usage | none | cpu usage |
+| system_load_average_1m | none | load |
+| jvm_memory_used_bytes | byte | jvm memory used |
+| jvm_memory_max_bytes | byte | jvm max memory |
+| jvm_gc_pause_seconds_count | none | gc count |
+| jvm_gc_pause_seconds_sum | second | gc time |
+| jvm_threads_daemon | none | jvm threads count |
+
+#### Metric set：Nacos
+
+| Metric name | Metric unit | Metric help description |
+| ----------- | ----------- | ----------- |
+| http_server_requests_seconds_count | second | http requests
count |
+| http_server_requests_seconds_sum | second | http requests
time |
+| nacos_timer_seconds_sum | second | Nacos config notify time |
+| nacos_timer_seconds_count | none | Nacos config notify count |
+| nacos_monitor{name='longPolling'} | none | Nacos config connection count |
+| nacos_monitor{name='configCount'} | none | Nacos configuration
file count |
+| nacos_monitor{name='dumpTask'} | none | Nacos config dump task count |
+| nacos_monitor{name='notifyTask'} | none | Nacos config notify task count |
+| nacos_monitor{name='getConfig'} | none | Nacos config read configuration
count |
+| nacos_monitor{name='publish'} | none | Nacos config update configuration
count |
+| nacos_monitor{name='ipCount'} | none | Nacos naming ip count |
+| nacos_monitor{name='domCount'} | none | Nacos naming domain count(1.x
version) |
+| nacos_monitor{name='serviceCount'} | none | Nacos naming domain count(2.x
version) |
+| nacos_monitor{name='failedPush'} | none | Nacos naming push fail count |
+| nacos_monitor{name='avgPushCost'} | second | Nacos naming push cost
time(average) |
+| nacos_monitor{name='leaderStatus'} | none | Nacos naming if node is leader |
+| nacos_monitor{name='maxPushCost'} | second | Nacos naming push cost
time(max) |
+| nacos_monitor{name='mysqlhealthCheck'} | none | Nacos naming mysql health
check count |
+| nacos_monitor{name='httpHealthCheck'} | none | Nacos naming http health
check count |
+| nacos_monitor{name='tcpHealthCheck'} | none | Nacos naming tcp health check
count |
+
+#### Metric set：Nacos exception
+
+| Metric name | Metric unit | Metric help description |
+| ----------- | ----------- | ----------- |
+| nacos_exception_total{name='db'} | none | database exception |
+| nacos_exception_total{name='configNotify'} | none | Nacos config
notify exception |
+| nacos_exception_total{name='unhealth'} | none | Nacos config server
health check exception |
+| nacos_exception_total{name='disk'} | none | Nacos naming write disk
exception |
+| nacos_exception_total{name='leaderSendBeatFailed'} | none | Nacos naming
leader send heart beat fail count |
+| nacos_exception_total{name='illegalArgument'} | none | request
argument illegal count |
+| nacos_exception_total{name='nacos'} | none | Nacos inner exception |
+
+#### Metric set：client
+
+| Metric name | Metric unit | Metric help description |
+| ----------- | ----------- | ----------- |
+| nacos_monitor{name='subServiceCount'} | none | subscribed
services count |
+| nacos_monitor{name='pubServiceCount'} | none | published services
count |
+| nacos_monitor{name='configListenSize'} | none | listened
configuration file count |
+| nacos_client_request_seconds_count | none | request count |
+| nacos_client_request_seconds_sum | second | request time |
+
\ No newline at end of file
diff --git a/home/docs/help/tidb.md b/home/docs/help/tidb.md
new file mode 100644
index 000000000..2a7bc5b65
--- /dev/null
+++ b/home/docs/help/tidb.md
@@ -0,0 +1,55 @@
+---
+id: tidb
+title: Monitoring：TiDB database monitoring
+sidebar_label: TiDB database
+keywords: [open source monitoring tool, open source database monitoring tool,
monitoring tidb database metrics]
+---
+
+> HertzBeat monitors general performance metrics of TiDB through HTTP and JDBC
protocol.
+
+[Metrics Schema](https://docs.pingcap.com/tidb/stable/metrics-schema)
+
+[METRICS_SUMMARY](https://docs.pingcap.com/tidb/stable/information-schema-metrics-summary)
+
+[METRICS_TABLES](https://docs.pingcap.com/tidb/stable/information-schema-metrics-tables)
+
+**Protocol Use: HTTP and JDBC**
+
+### Configuration parameter
+
+| Parameter name | Parameter help description |
+| ----------- | ----------- |
+| Target Host | Monitored IPV4, IPV6 or domain name. Note⚠️Without
protocol header (eg: https://, http://) |
+| Task name | Identify the name of this monitoring. The name needs to be
unique |
+| Service Port | The port that the TiDB database provides externally for
status reporting is 10080 by default |
+| PD Port | The PD port for the TiDB database, which defaults to 2379 |
+| Query timeout | Set the timeout time when SQL query does not respond to
data, unit: ms, default: 6000ms |
+| JDBC Port | The TiDB database externally provides the port used for
client requests, which defaults to 4000 |
+| Database name | Database instance name, optional |
+| Username | Database connection user name, optional |
+| Password | Database connection password, optional |
+| JDBC URL | Database using
[JDBC](https://docs.pingcap.com/tidb/stable/dev-guide-connect-to-tidb#jdbc)
connection URL，optional，If configured, the database name, user name, password
and other parameters in the URL will overwrite the above configured parameters |
+| Collection interval | Interval time of monitor periodic data collection,
unit: second, and the minimum interval that can be set is 30 seconds |
+| Whether to detect | Whether to detect and check the availability of
monitoring before adding monitoring. Adding and modifying operations will
continue only after the detection is successful |
+| Description remarks | For more information about identifying and
describing this monitoring, users can note information here |
+
+
+### Collection Metric
+
+The monitoring template will retrieve the monitoring metrics from the TiDB
System Variables table, and the user can retrieve the [TiDB System Variables
Table](https://docs.pingcap.com/tidb/stable/system-variables) by himself to
query the required information or other system variables.
+
+Besides, TiDB also provides default monitoring metrics table, see [Metrics
Schema](https://docs.pingcap.com/tidb/stable/metrics-schema) and
[METRICS_SUMMARY](https://docs.pingcap.com/tidb/stable/information-schema-metrics-summary),
and users can add their own sql codes according to their needs.
+
+Due to the large number of metrics that can be monitored, only the metrics
queried in the monitoring template are described below.
+
+#### Metric set: global variables
+
+| Metric Name | Metric Unit | Metric Help Description
[...]
+|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
+| version | none | The MySQL version, followed by the TiDB
version. For example '8.0.11-TiDB-v7.5.1'.
[...]
+| version_comment | none | The TiDB version. For example, 'TiDB
Server (Apache License 2.0) Community Edition, MySQL 8.0 compatible'.
[...]
+| version_compile_machine | none | The name of the CPU
architecture on which TiDB is running.
|
+| version_compile_os | none | The name of the OS on which TiDB
is running.
|
+| max_connections | none | The maximum number of concurrent
connections permitted for a single TiDB instance. This variable can be used for
resources control. The default value 0 means no limit. When the value of this
variable is larger than 0, and the number of connections reaches the value, the
TiDB server rejects new connections from clients.
[...]
+| datadir | none | The location where data is stored. This location
can be a local path /tmp/tidb, or point to a PD server if the data is stored on
TiKV. A value in the format of ${pd-ip}:${pd-port} indicates the PD server that
TiDB connects to on startup.
[...]
+| port | none | The port that the tidb-server is listening on when
speaking the MySQL protocol.
|
diff --git
a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/guide.md
b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/guide.md
index 991c8ad74..207936f8e 100644
--- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/guide.md
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/guide.md
@@ -33,6 +33,7 @@ sidebar_label: 帮助入门
 👉 [达梦数据库监控](dm) <br />
 👉 [OpenGauss数据库监控](opengauss) <br />
 👉 [IoTDB数据库监控](iotdb) <br />
+  👉 [TiDB数据库监控](tidb) <br />
### 操作系统监控
@@ -51,6 +52,7 @@ sidebar_label: 帮助入门
 👉 [RabbitMQ](rabbitmq) <br />
 👉 [ActiveMQ](activemq) <br />
 👉 [Jetty](jetty) <br />
+  👉 [Nacos](nacos) <br />
### 云原生监控
diff --git
a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/nacos.md
b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/nacos.md
new file mode 100644
index 000000000..ef643cf2f
--- /dev/null
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/nacos.md
@@ -0,0 +1,93 @@
+---
+id: nacos
+title: 监控：Nacos分布式监控
+sidebar_label: Nacos分布式
+keywords: [开源监控系统, 中间件监控, Nacos分布式监控]
+---
+
+> 通过调用 Nacos Metrics 接口对 Nacos 注册配置中心服务的通用指标进行采集监控。
+
+### 监控前操作
+
+#### 搭建Nacos集群暴露metrics数据
+
+1. 按照[部署文档](https://nacos.io/zh-cn/docs/deployment.html)搭建好Nacos集群。
+2. 配置application.properties文件，暴露metrics数据。
+```
+management.endpoints.web.exposure.include=*
+```
+3. 访问```{ip}:8848/nacos/actuator/prometheus```，查看是否能访问到metrics数据。
+
+更多信息请参考[Nacos 监控手册](https://nacos.io/zh-cn/docs/monitor-guide.html)。
+
+### 配置参数
+
+| 参数名称 | 参数帮助描述 |
+| ----------- | ----------- |
+| 服务器Host | 被监控的对端IPV4，IPV6或域名。注意⚠️不带协议头(eg: https://, http://)。 |
+| 任务名称 | 标识此监控的名称，名称需要保证唯一性。 |
+| Nacos服务端口 | Nacos服务对外提供的端口，默认为8848。 |
+| 采集间隔 | 监控周期性采集数据间隔时间，单位秒，可设置的最小间隔为30秒 |
+| 描述备注 | 更多标识和描述此监控的备注信息，用户可以在这里备注信息 |
+
+### 采集指标
+
+#### 指标集合：jvm
+
+| 指标名称 | 指标单位 | 指标帮助描述 |
+| ----------- | ----------- | ----------- |
+| system_cpu_usage | 无 | CPU使用率 |
+| system_load_average_1m | 无 | load |
+| jvm_memory_used_bytes | 字节 | 内存使用字节，包含各种内存区 |
+| jvm_memory_max_bytes | 字节 | 内存最大字节，包含各种内存区 |
+| jvm_gc_pause_seconds_count | 无 | gc次数，包含各种gc |
+| jvm_gc_pause_seconds_sum | 秒 | gc耗时，包含各种gc |
+| jvm_threads_daemon | 无 | 线程数 |
+
+#### 指标集合：Nacos
+
+| 指标名称 | 指标单位 | 指标帮助描述 |
+| ----------- | ----------- | ----------- |
+| http_server_requests_seconds_count | 秒 | http请求次数，包括多种(url,方法,code) |
+| http_server_requests_seconds_sum | 秒 |
http请求总耗时，包括多种(url,方法,code) |
+| nacos_timer_seconds_sum | 秒 | Nacos config水平通知耗时 |
+| nacos_timer_seconds_count | 无 | Nacos config水平通知次数 |
+| nacos_monitor{name='longPolling'} | 无 | Nacos config长连接数 |
+| nacos_monitor{name='configCount'} | 无 | Nacos config配置个数 |
+| nacos_monitor{name='dumpTask'} | 无 | Nacos config配置落盘任务堆积数 |
+| nacos_monitor{name='notifyTask'} | 无 | Nacos config配置水平通知任务堆积数 |
+| nacos_monitor{name='getConfig'} | 无 | Nacos config读配置统计数 |
+| nacos_monitor{name='publish'} | 无 | Nacos config写配置统计数 |
+| nacos_monitor{name='ipCount'} | 无 | Nacos naming ip个数 |
+| nacos_monitor{name='domCount'} | 无 | Nacos naming域名个数(1.x 版本) |
+| nacos_monitor{name='serviceCount'} | 无 | Nacos naming域名个数(2.x 版本) |
+| nacos_monitor{name='failedPush'} | 无 | Nacos naming推送失败数 |
+| nacos_monitor{name='avgPushCost'} | 秒 | Nacos naming平均推送耗时 |
+| nacos_monitor{name='leaderStatus'} | 无 | Nacos naming角色状态 |
+| nacos_monitor{name='maxPushCost'} | 秒 | Nacos naming最大推送耗时 |
+| nacos_monitor{name='mysqlhealthCheck'} | 无 | Nacos naming mysql健康检查次数 |
+| nacos_monitor{name='httpHealthCheck'} | 无 | Nacos naming http健康检查次数 |
+| nacos_monitor{name='tcpHealthCheck'} | 无 | Nacos naming tcp健康检查次数 |
+
+#### 指标集合：Nacos 异常
+
+| 指标名称 | 指标单位 | 指标帮助描述 |
+| ----------- | ----------- | ----------- |
+| nacos_exception_total{name='db'} | 无 | 数据库异常 |
+| nacos_exception_total{name='configNotify'} | 无 | Nacos
config水平通知失败 |
+| nacos_exception_total{name='unhealth'} | 无 | Nacos config
server之间健康检查异常 |
+| nacos_exception_total{name='disk'} | 无 | Nacos naming写磁盘异常 |
+| nacos_exception_total{name='leaderSendBeatFailed'} | 无 | Nacos naming
leader发送心跳异常 |
+| nacos_exception_total{name='illegalArgument'} | 无 | 请求参数不合法 |
+| nacos_exception_total{name='nacos'} | 无 | Nacos请求响应内部错误异常（读写失败，没权限，参数错误） |
+
+#### 指标集合：client
+
+| 指标名称 | 指标单位 | 指标帮助描述 |
+| ----------- | ----------- | ----------- |
+| nacos_monitor{name='subServiceCount'} | 无 | 订阅的服务数 |
+| nacos_monitor{name='pubServiceCount'} | 无 | 发布的服务数 |
+| nacos_monitor{name='configListenSize'} | 无 | 监听的配置数 |
+| nacos_client_request_seconds_count | 无 | 请求的次数，包括多种(url,方法,code) |
+| nacos_client_request_seconds_sum | 秒 | 请求的总耗时，包括多种(url,方法,code) |
+
\ No newline at end of file
diff --git
a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/tidb.md
b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/tidb.md
new file mode 100644
index 000000000..cf0cfb417
--- /dev/null
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/tidb.md
@@ -0,0 +1,49 @@
+---
+id: tidb
+title: 监控：TiDB数据库监控
+sidebar_label: TiDB数据库
+keywords: [开源监控系统, 开源数据库监控, TiDB数据库监控]
+---
+
+> 使用 HTTP 和 JDBC 协议对 TiDB 的通用性能指标进行采集监控。
+
+### 配置参数
+
+| 参数名称 | 参数帮助描述 |
+| ----------- | ----------- |
+| 目标Host | 被监控的对端IPV4，IPV6或域名。注意⚠️不带协议头(eg: https://, http://)。 |
+| 任务名称 | 标识此监控的名称，名称需要保证唯一性。 |
+| Service端口 | TiDB数据库对外提供用于状态报告的端口，默认为10080。 |
+| PD端口 | TiDB数据库的PD端口，默认为2379。 |
+| 查询超时时间 | 设置SQL查询未响应数据时的超时时间，单位ms毫秒，默认6000毫秒。 |
+| JDBC端口 | TiDB数据库对外提供用于客户端请求的端口，默认为4000。 |
+| 数据库名称 | 数据库实例名称，可选。 |
+| 用户名 | 数据库连接用户名，可选 |
+| 密码 | 数据库连接密码，可选 |
+| JDBC URL |
数据库使用[JDBC驱动的](https://docs.pingcap.com/zh/tidb/stable/dev-guide-connect-to-tidb#jdbc)连接URL，可选，若配置，则URL里面的数据库名称，用户名密码等参数会覆盖上面配置的参数
|
+| 采集间隔 | 监控周期性采集数据间隔时间，单位秒，可设置的最小间隔为30秒 |
+| 是否探测 | 新增监控前是否先探测检查监控可用性，探测成功才会继续新增修改操作 |
+| 描述备注 | 更多标识和描述此监控的备注信息，用户可以在这里备注信息 |
+
+### 采集指标
+
+监控模板将从TiDB系统变量表中检索监控指标，用户可以自行检索[TiDB系统变量表](https://docs.pingcap.com/zh/tidb/stable/system-variables)以查询所需信息或其他系统变量。
+
+除此之外，TiDB也提供默认监控指标表，见[Metrics
Schema](https://docs.pingcap.com/zh/tidb/stable/metrics-schema)与[METRICS_SUMMARY](https://docs.pingcap.com/zh/tidb/stable/information-schema-metrics-summary)，用户可以根据需求自行添加检索式。
+
+由于可以被监控的指标过多，下文仅介绍监控模板中所查询的指标。
+
+#### 指标集合：系统变量
+
+| 指标名称 | 指标单位 | 指标帮助描述 |
+| ----------- | ----------- | ----------- |
+| version | 无 | MySQL 的版本和 TiDB 的版本，例如 '8.0.11-TiDB-v7.5.1' |
+| version_comment | 无 | TiDB 版本号的其他信息，例如 'TiDB Server (Apache License
2.0) Community Edition, MySQL 8.0 compatible' |
+| version_compile_machine | 无 | 运行 TiDB 的 CPU 架构的名称 |
+| version_compile_os | 无 | TiDB 所在操作系统的名称 |
+| max_connections | 无 | 该变量表示 TiDB 中同时允许的最大客户端连接数，用于资源控制。默认情况下，该变量值为 0
表示不限制客户端连接数。当本变量的值大于 0 且客户端连接数到达此值时，TiDB 服务端将会拒绝新的客户端连接。 |
+| datadir | 无 | 数据存储的位置，位置可以是本地路径 /tmp/tidb。如果数据存储在 TiKV 上，则可以是指向
PD 服务器的路径。变量值的格式为 ${pd-ip}:${pd-port}，表示 TiDB 在启动时连接到的 PD 服务器。 |
+| port | 无 | 使用 MySQL 协议时 tidb-server 监听的端口。 |
+
+
+
diff --git a/home/sidebars.json b/home/sidebars.json
index c552c4fe2..194b16fd6 100644
--- a/home/sidebars.json
+++ b/home/sidebars.json
@@ -163,7 +163,9 @@
"help/oracle",
"help/dm",
"help/opengauss",
- "help/nebulaGraph"
+ "help/nebulaGraph",
+ "help/tidb"
+
]
},
{
@@ -192,7 +194,8 @@
"help/shenyu",
"help/rabbitmq",
"help/activemq",
- "help/spring_gateway"
+ "help/spring_gateway",
+ "help/nacos"
]
},
{
@@ -265,9 +268,11 @@
"type": "category",
"label": "Others",
"items": [
+ "others/developer",
"others/contributing",
"others/resource"
]
}
]
-}
\ No newline at end of file
+}
+
diff --git a/manager/src/main/resources/define/app-tidb.yml
b/manager/src/main/resources/define/app-tidb.yml
index e18adf80d..b3519b4f4 100644
--- a/manager/src/main/resources/define/app-tidb.yml
+++ b/manager/src/main/resources/define/app-tidb.yml
@@ -28,7 +28,7 @@ name:
# 监控类型的帮助描述信息
help:
zh-CN: HertzBeat 使用 HTTP 和 JDBC 协议对 TiDB
的通用性能指标进行采集监控，点击查看开启步骤</a>。<br>您可以点击“<i>新建 TiDB
数据库</i>”并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
- en-US: HertzBeat monitors general performance metrics of TiDB through HTTP
adn JDBC protocol. <br> You could click the "<i>New TiDB</i>" button and
proceed with the configuration or import an existing setup through the "<i>More
Actions</i>".
+ en-US: HertzBeat monitors general performance metrics of TiDB through HTTP
and JDBC protocol. <br> You could click the "<i>New TiDB</i>" button and
proceed with the configuration or import an existing setup through the "<i>More
Actions</i>".
zh-TW: HertzBeat 使用 HTTP 和 JDBC 協議對 TiDB 的通用性能指標進行採集監控，點擊查看開啟步驟</a>。
<br>您可以點擊“<i>新建 TiDB 數據庫</i>”並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
helpLink:
zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/tidb
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
