TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. Try AI-powered Chat2Query free at : https://www.pingcap.com/tidb-serverless/
The PR https://github.com/pingcap/tidb/pull/13481 proposes a new method of acquiring diagnostic information in TiDB and exposing diagnostic information by the system tables so that users can query using SQL. The purpose of the proposal #13481 is aim to improve the efficiency of the cluster-based information query, state acquisition, log retrieval, one-click inspection, and fault diagnosis
Note
This issue is a TODO list catalog that is used to clarify the split details of the entire feature. If you are interested in a part, use the following workflow:
Select the module you are interested in.
Create a new issue to claim the relevant work and describe the rough implementation in the new issue.
File a new pull request.
Issues:
Protocol Definition
[x] Define the Diagnostics gRPC Service and the related message type in kvproto #13581 @lonng
Information Collection
Cluster Topology
Add a system table to provide cluster topology
[x] TiDB #13035 @lonng
[x] The current implementation should be refined and the ID and NAME columns should be deleted #13586 @lonng
Cluster Configuration
Add a system table to provide cluster configuration
[x] TiDB #13063 @lonng
[x] TiKV #13063 @lonng
[x] PD #13063 @lonng
[x] TiDB: Predicates push down #13832 @lonng
Cluster Performance Sampling
Add HTTP API for cluster components to get performance sample data
Process information: current process name, command line parameters, executable file path, pid, environment variables, memory, startup time, uid, gid, process status
The PR https://github.com/pingcap/tidb/pull/13481 proposes a new method of acquiring diagnostic information in TiDB and exposing diagnostic information by the system tables so that users can query using SQL. The purpose of the proposal #13481 is aim to improve the efficiency of the cluster-based information query, state acquisition, log retrieval, one-click inspection, and fault diagnosis
Note
This issue is a TODO list catalog that is used to clarify the split details of the entire feature. If you are interested in a part, use the following workflow:
Issues:
Diagnostics gRPC Service
and the related message type in kvproto #13581 @lonngID
andNAME
columns should be deleted #13586 @lonngUSB device listFile descriptor information: Available Quantity, Current Used QuantityLogicalMemTable
part fromDataSource
#13741 @lonngremote-metrics-storage
configurationTeachability, Documentation, Adoption, Migration Strategy:
Proposal: https://github.com/pingcap/tidb/pull/13481