From fda725169a98ad431e752de263c6c54a0e22aef0 Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Tue, 22 Sep 2026 11:06:15 +0800 Subject: [PATCH 1/5] Update monitor-built-in-alerting.md --- tidb-cloud/monitor-built-in-alerting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 084348c4c9b76..532f12fa226b0 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -126,7 +126,7 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud -### Performance overview alerts +### Performance overview alerts | Condition | Recommended Action | |:--- |:--- | From 2eadf5a3d1458f4ca88b3bd434580b07f98c45e1 Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Tue, 22 Sep 2026 11:13:25 +0800 Subject: [PATCH 2/5] docs: add Query Latency Count Threshold alerts to Performance overview alerts table --- tidb-cloud/monitor-built-in-alerting.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 532f12fa226b0..984a9e2e9bcd9 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -135,6 +135,9 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud | Query P99 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Query P95 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Request error rate exceeds 10% | Review recent errors and the overall statement execution status for the cluster.| +| More than 20 SQL statements exceeded 256 ms within 1 minute | This is an early-warning signal based on latency metrics. Because TiDB's slow log only records queries that exceed 300 ms by default, not every counted query is guaranteed to have a matching entry in the slow query list.
  1. Check for recent schema or index changes.
  2. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| More than 20 SQL statements exceeded 512 ms within 1 minute |
  1. Check for recent schema or index changes.
  2. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| More than 20 SQL statements exceeded 4096 ms within 1 minute |
  1. Check for recent schema or index changes.
  2. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| ### Changefeed alerts for {{{ .essential }}} and {{{ .premium }}} From 29ca6b48f9bfdddbcb3c9b89acb572e01d170bce Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Tue, 22 Sep 2026 18:19:32 +0800 Subject: [PATCH 3/5] Update monitor-built-in-alerting.md --- tidb-cloud/monitor-built-in-alerting.md | 32 +++++++++++++++++++++---- 1 file changed, 27 insertions(+), 5 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 984a9e2e9bcd9..f5e16ce2f1f90 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -124,7 +124,32 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud - + + +### Performance overview alerts + +| Condition | Recommended Action | +|:--- |:--- | +| Request units per second (RU/s) exceed 80% of the maximum RCU |
  1. Review RU metrics to determine whether the increase is gradual or a sudden spike.
  2. If the increase is gradual, check whether query duration has increased. If so, the current maximum RCU might be insufficient.
  3. Scale capacity by manually increasing the maximum RCU in the TiDB Cloud console.

If you cannot resolve the issue, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| QPS drops by 80% |
  1. Check whether the drop is caused by increasing query latency.
  2. Verify that your application is operating normally. If the drop is intentional, ignore this alert. If the drop is unintentional and you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.
| +| Query P99 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| +| Query P95 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| +| Request error rate exceeds 10% | Review recent errors and the overall statement execution status for the cluster.| +| More than 20 SQL statements exceeded 256 ms within 1 minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| More than 20 SQL statements exceeded 512 ms within 1 minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| More than 20 SQL statements exceeded 4096 ms within 1 minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| + +### Changefeed alerts for {{{ .premium }}} + +| Condition | Recommended Action | +|:--------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The changefeed latency exceeds 600 seconds. | Check the changefeed status on the **Changefeed** page and **Changefeed Detail** page of the TiDB Cloud console, where you can find some error messages to help diagnose this issue.
Possible reasons that can trigger this alert include:If the problem cannot be fixed from your side, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance. | +| The changefeed status is `FAILED`. | Check the changefeed status on the **Changefeed** page and **Changefeed Detail** page of the TiDB Cloud console, where you can find some error messages to help diagnose this issue.
If the problem cannot be fixed from your side, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| +| The changefeed status is `WARNING`. | Check the changefeed status on the **Changefeed** page and **Changefeed Detail** page of the TiDB Cloud console, where you can find some error messages to help diagnose this issue.
If the problem cannot be fixed from your side, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| + + + + ### Performance overview alerts @@ -135,11 +160,8 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud | Query P99 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Query P95 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Request error rate exceeds 10% | Review recent errors and the overall statement execution status for the cluster.| -| More than 20 SQL statements exceeded 256 ms within 1 minute | This is an early-warning signal based on latency metrics. Because TiDB's slow log only records queries that exceed 300 ms by default, not every counted query is guaranteed to have a matching entry in the slow query list.
  1. Check for recent schema or index changes.
  2. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| -| More than 20 SQL statements exceeded 512 ms within 1 minute |
  1. Check for recent schema or index changes.
  2. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| -| More than 20 SQL statements exceeded 4096 ms within 1 minute |
  1. Check for recent schema or index changes.
  2. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| -### Changefeed alerts for {{{ .essential }}} and {{{ .premium }}} +### Changefeed alerts for {{{ .essential }}} | Condition | Recommended Action | |:--------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| From b2cdc78950b9c669ba46471fcc24ff668ad1b02c Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Mon, 28 Sep 2026 22:56:20 +0800 Subject: [PATCH 4/5] Apply suggestions from code review --- tidb-cloud/monitor-built-in-alerting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index f5e16ce2f1f90..4ea992b9d2114 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -126,7 +126,7 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud -### Performance overview alerts +### Performance overview alerts for {{{ .premium }}} | Condition | Recommended Action | |:--- |:--- | @@ -151,7 +151,7 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud -### Performance overview alerts +### Performance overview alerts for {{{ .essential }}} | Condition | Recommended Action | |:--- |:--- | From 511763347e573aff55466fff7f2cafe2a8c55539 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 29 Sep 2026 15:55:07 +0800 Subject: [PATCH 5/5] Update tidb-cloud/monitor-built-in-alerting.md --- tidb-cloud/monitor-built-in-alerting.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 4ea992b9d2114..cc3fca9e3a83a 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -135,9 +135,9 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud | Query P99 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Query P95 latency exceeds 200 ms |
  1. Investigate slow queries: go to the Slow Query page and filter by a recent time range to identify newly introduced or slower-running queries.
  2. Review recent changes, such as application deployments, schema changes, or data import jobs, that might have affected traffic patterns.

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Request error rate exceeds 10% | Review recent errors and the overall statement execution status for the cluster.| -| More than 20 SQL statements exceeded 256 ms within 1 minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| -| More than 20 SQL statements exceeded 512 ms within 1 minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| -| More than 20 SQL statements exceeded 4096 ms within 1 minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| More than 20 SQL statements exceed a latency threshold of 256 ms within one minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| More than 20 SQL statements exceed a latency threshold of 512 ms within one minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| +| More than 20 SQL statements exceed a latency threshold of 4,096 ms within one minute | Check for recent schema or index changes. Review the slow query list in the TiDB Cloud console. It might take several minutes for the corresponding slow query records to appear. If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).| ### Changefeed alerts for {{{ .premium }}}