Skip to content

Commit 680ab1a

Browse files
authored
v5.4-v6.1: update TiDB in Kubernetes links from dev to v1.4 (pingcap#22080) (pingcap#22083)
1 parent 88d8a40 commit 680ab1a

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

dashboard/continuous-profiling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ To enable Continuous Profiling on clusters deployed using TiUP, perform the foll
4848

4949
### Clusters deployed using TiDB Operator
5050

51-
See [Enable continuous profiling](https://docs.pingcap.com/tidb-in-kubernetes/dev/access-dashboard#enable-continuous-profiling).
51+
See [Enable continuous profiling](https://docs.pingcap.com/tidb-in-kubernetes/v1.4/access-dashboard#enable-continuous-profiling).
5252

5353
## Access the page
5454

dashboard/dashboard-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ To clear your browser cache, take the following steps:
8383

8484
### A `required component NgMonitoring is not started` error is shown
8585

86-
NgMonitoring is an advanced monitoring component built in TiDB clusters of v5.4.0 and later versions. It supports such features as **Continuous Profiling** and **Top SQL**. In a TiDB cluster deployed using TiUP, NgMonitoring is deployed automatically. In a TiDB cluster deployed using TiDB Operator, you need to deploy NgMonitoring manually by referring to [Enable Continuous Profiling](https://docs.pingcap.com/tidb-in-kubernetes/dev/access-dashboard/#enable-continuous-profiling).
86+
NgMonitoring is an advanced monitoring component built in TiDB clusters of v5.4.0 and later versions. It supports such features as **Continuous Profiling** and **Top SQL**. In a TiDB cluster deployed using TiUP, NgMonitoring is deployed automatically. In a TiDB cluster deployed using TiDB Operator, you need to deploy NgMonitoring manually by referring to [Enable Continuous Profiling](https://docs.pingcap.com/tidb-in-kubernetes/v1.4/access-dashboard/#enable-continuous-profiling).
8787

8888
If the **Continuous Profiling** page shows `required component NgMonitoring is not started`, address the problem based on the deployment method of the TiDB cluster.
8989

@@ -145,4 +145,4 @@ After performing the preceding steps, enable Continuous Profiling on TiDB Dashbo
145145

146146
#### Clusters deployed using TiDB Operator
147147

148-
Deploy NgMonitoring by referring to [Enable Continuous Profiling](https://docs.pingcap.com/tidb-in-kubernetes/dev/access-dashboard/#enable-continuous-profiling).
148+
Deploy NgMonitoring by referring to [Enable Continuous Profiling](https://docs.pingcap.com/tidb-in-kubernetes/v1.4/access-dashboard/#enable-continuous-profiling).

0 commit comments

Comments
 (0)