From 39e0d99986b6ff387a52a81dc1655e4403364c11 Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Fri, 30 Jan 2026 14:38:04 +0800 Subject: [PATCH 01/17] Update monitor-alert-flashduty.md --- tidb-cloud/monitor-alert-flashduty.md | 47 ++++++++++++++++++++++++--- 1 file changed, 43 insertions(+), 4 deletions(-) diff --git a/tidb-cloud/monitor-alert-flashduty.md b/tidb-cloud/monitor-alert-flashduty.md index e580cc130f8ba..179d90a755527 100644 --- a/tidb-cloud/monitor-alert-flashduty.md +++ b/tidb-cloud/monitor-alert-flashduty.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is only available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. ## Prerequisites @@ -19,7 +19,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via ## Subscribe to alert notifications -To receive alert notifications of clusters in your project, take the following steps: +To receive alert notifications of clusters, take the following steps: ### Step 1. Generate a Flashduty webhook URL @@ -28,6 +28,10 @@ To receive alert notifications of clusters in your project, take the following s ### Step 2. Subscribe from TiDB Cloud +Alert notification subscriptions vary by product tier. + + + > **Tip:** > > The alert subscription is for all alerts in the current project. If you have multiple clusters in the project, you just need to subscribe once. @@ -44,15 +48,50 @@ To receive alert notifications of clusters in your project, take the following s 7. Click **Save** to complete the subscription. -Alternatively, you can also click **Subscribe** in the upper-right corner of the **Alert** page of the cluster. You will be directed to the **Alert Subscriber** page. + + + + +> **Tip:** +> +> The alert subscription is for all alerts in the current cluster. If you have multiple clusters, you need to subscribe to each one individually. + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, click **Add Subscriber** in the upper-right corner. +4. Select **Flashduty** from the **Subscriber Type** drop-down list. +5. Enter a name in the **Name** field and your Flashduty webhook URL in the **Webhook URL** field. +6. Click **Test Connection**. + + - If the test succeeds, the **Save** button is displayed. + - If the test fails, an error message is displayed. Follow the message to troubleshoot the issue and retry the connection. + +7. Click **Save** to complete the subscription. + + + +Alternatively, you can also click **Subscribe** in the upper-right corner of the **Alert** page of the cluster. You will be directed to the **Alert Subscription** page. If an alert condition remains unchanged, the alert sends notifications every three hours. ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications of clusters in your project, take the following steps: +If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. + + 1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner. 2. In the left navigation pane, click **Project Settings** > **Alert Subscription**. 3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. 4. Click **Unsubscribe** to confirm the unsubscription. + + + + + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. +4. Click **Unsubscribe** to confirm the unsubscription. + + From b67cf5ec3abaa6be4dac1c9966d0dd7108c07acd Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Fri, 30 Jan 2026 14:59:06 +0800 Subject: [PATCH 02/17] Update monitor-alert-zoom.md --- tidb-cloud/monitor-alert-zoom.md | 45 +++++++++++++++++++++++++++++--- 1 file changed, 42 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/monitor-alert-zoom.md b/tidb-cloud/monitor-alert-zoom.md index 21755ea0aea71..9bf676bac5499 100644 --- a/tidb-cloud/monitor-alert-zoom.md +++ b/tidb-cloud/monitor-alert-zoom.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is only available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. ## Prerequisites @@ -45,6 +45,10 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via ### Step 3. Subscribe from TiDB Cloud +Alert notification subscriptions vary by product tier. + + + > **Tip:** > > The alert subscription is for all alerts in the current project. If you have multiple clusters in the project, you just need to subscribe once. @@ -61,15 +65,50 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via 7. Click **Save** to complete the subscription. -Alternatively, you can also click **Subscribe** in the upper-right corner of the **Alert** page of the cluster. You will be directed to the **Alert Subscriber** page. + + + + +> **Tip:** +> +> The alert subscription is for all alerts in the current cluster. If you have multiple clusters, you need to subscribe to each one individually. + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, click **Add Subscriber** in the upper-right corner. +4. Select **Zoom** from the **Subscriber Type** drop-down list. +5. Enter a name in the **Name** field, your Zoom webhook URL in the **URL** field, and the verification token in the **Token** field. +6. Click **Test Connection**. + + - If the test succeeds, the **Save** button is displayed. + - If the test fails, an error message is displayed. Follow the message to troubleshoot the issue and retry the connection. + +7. Click **Save** to complete the subscription. + + + +Alternatively, you can also click **Subscribe** in the upper-right corner of the **Alert** page of the cluster. You will be directed to the **Alert Subscription** page. If an alert condition remains unchanged, the alert sends notifications every three hours. ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications of clusters in your project, take the following steps: +If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. + + 1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner. 2. In the left navigation pane, click **Project Settings** > **Alert Subscription**. 3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. 4. Click **Unsubscribe** to confirm the unsubscription. + + + + + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. +4. Click **Unsubscribe** to confirm the unsubscription. + + From 43eda6074920c14a3aca5dd727b61a3f7e73d2f1 Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Fri, 30 Jan 2026 15:20:54 +0800 Subject: [PATCH 03/17] Update monitor-alert-email.md --- tidb-cloud/monitor-alert-email.md | 49 +++++++++++++++++++++++++++---- 1 file changed, 43 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/monitor-alert-email.md b/tidb-cloud/monitor-alert-email.md index 0376a0b8cc03e..6f2481fcc2513 100644 --- a/tidb-cloud/monitor-alert-email.md +++ b/tidb-cloud/monitor-alert-email.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is only available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. ## Prerequisites @@ -17,12 +17,14 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via ## Subscribe to alert notifications +To receive alert notifications, take the following steps. The steps vary by product tier. + + + > **Tip:** > > The alert subscription is for all alerts in the current project. If you have multiple clusters in the project, you just need to subscribe once. -To get alert notifications of clusters in your project, take the following steps: - 1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner. 2. In the left navigation pane, click **Project Settings** > **Alert Subscription**. 3. On the **Alert Subscription** page, click **Add Subscriber** in the upper-right corner. @@ -34,16 +36,51 @@ To get alert notifications of clusters in your project, take the following steps - If the test fails, an error message is displayed. Follow the message to troubleshoot the issue and then retry the connection. 7. Click **Save** to complete the subscription. + + + + + +> **Tip:** +> +> The alert subscription is for all alerts in the current cluster. If you have multiple clusters, you need to subscribe to each one individually. + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, click **Add Subscriber** in the upper-right corner. +4. Select **Email** from the **Subscriber Type** drop-down list. +5. Enter your email address. +6. Click **Test Connection**. + + - If the test succeeds, the **Save** button is displayed. + - If the test fails, an error message is displayed. Follow the message to troubleshoot the issue and then retry the connection. + +7. Click **Save** to complete the subscription. + + -Alternatively, you can also click **Subscribe** in the upper-right corner of the [**Alert**](/tidb-cloud/monitor-built-in-alerting.md#view-alerts) page of the cluster. You will be directed to the **Alert Subscriber** page. +Alternatively, you can also click **Subscribe** in the upper-right corner of the [**Alert**](/tidb-cloud/monitor-built-in-alerting.md#view-alerts) page of the cluster. You will be directed to the **Alert Subscription** page. If an alert condition remains unchanged, the alert sends email notifications every three hours. ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications of clusters in your project, take the following steps: +If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. + + 1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner. 2. In the left navigation pane, click **Project Settings** > **Alert Subscription**. 3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. -4. Click **Unsubscribe** to confirm the unsubscription. \ No newline at end of file +4. Click **Unsubscribe** to confirm the unsubscription. + + + + + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. +4. Click **Unsubscribe** to confirm the unsubscription. + + From 90c834c0fc8bcd74563191076b01ff00ca29d538 Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Fri, 30 Jan 2026 15:25:44 +0800 Subject: [PATCH 04/17] Update monitor-alert-slack.md --- tidb-cloud/monitor-alert-slack.md | 48 +++++++++++++++++++++++++++---- 1 file changed, 42 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/monitor-alert-slack.md b/tidb-cloud/monitor-alert-slack.md index dc38b6e5800dc..1cee6084d79f9 100644 --- a/tidb-cloud/monitor-alert-slack.md +++ b/tidb-cloud/monitor-alert-slack.md @@ -7,13 +7,10 @@ summary: Learn how to monitor your TiDB cluster by getting alert notifications v TiDB Cloud provides you with an easy way to subscribe to alert notifications via Slack, [email](/tidb-cloud/monitor-alert-email.md), [Zoom](/tidb-cloud/monitor-alert-zoom.md), [Flashduty](/tidb-cloud/monitor-alert-flashduty.md), and [PagerDuty](/tidb-cloud/monitor-alert-pagerduty.md). This document describes how to subscribe to alert notifications via Slack. -The following screenshot shows two example alerts. - -![TiDB Cloud Alerts in Slack](/media/tidb-cloud/tidb-cloud-alert-subscription.png) > **Note:** > -> Currently, alert subscription is only available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. ## Prerequisites @@ -35,6 +32,10 @@ You can see a new entry under the **Webhook URLs for Your Workspace** section in ### Step 2. Subscribe from TiDB Cloud +Alert notification subscriptions vary by product tier. + + + > **Tip:** > > The alert subscription is for all alerts in the current project. If you have multiple clusters in the project, you just need to subscribe once. @@ -51,15 +52,50 @@ You can see a new entry under the **Webhook URLs for Your Workspace** section in 7. Click **Save** to complete the subscription. + + + + +> **Tip:** +> +> The alert subscription is for all alerts in the current cluster. If you have multiple clusters, you need to subscribe to each one individually. + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, click **Add Subscriber** in the upper-right corner. +4. Select **Slack** from the **Subscriber Type** drop-down list. +5. Enter a name in the **Name** field and your Slack webhook URL in the **URL** field. +6. Click **Test Connection**. + + - If the test succeeds, the **Save** button is displayed. + - If the test fails, an error message is displayed. Follow the message to troubleshoot the issue and retry the connection. + +7. Click **Save** to complete the subscription. + + + Alternatively, you can also click **Subscribe** in the upper-right corner of the **Alert** page of the cluster. You will be directed to the **Alert Subscriber** page. If an alert condition remains unchanged, the alert sends notifications every three hours. ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications of clusters in your project, take the following steps: +If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. + + 1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner. 2. In the left navigation pane, click **Project Settings** > **Alert Subscription**. 3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. -4. Click **Unsubscribe** to confirm the unsubscription. \ No newline at end of file +4. Click **Unsubscribe** to confirm the unsubscription. + + + + + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. +4. Click **Unsubscribe** to confirm the unsubscription. + + From 742cc7877ae23ba6e28a73e229a618ebc2919097 Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Fri, 30 Jan 2026 15:30:11 +0800 Subject: [PATCH 05/17] Update monitor-alert-pagerduty.md --- tidb-cloud/monitor-alert-pagerduty.md | 46 +++++++++++++++++++++++++-- 1 file changed, 43 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/monitor-alert-pagerduty.md b/tidb-cloud/monitor-alert-pagerduty.md index b049b3be0ee3f..264a1c7f8174d 100644 --- a/tidb-cloud/monitor-alert-pagerduty.md +++ b/tidb-cloud/monitor-alert-pagerduty.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is only available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. ## Prerequisites @@ -19,7 +19,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via ## Subscribe to alert notifications -To receive alert notifications of clusters in your project, take the following steps: +To receive alert notifications, take the following steps: ### Step 1. Generate a PagerDuty integration key @@ -28,6 +28,10 @@ To receive alert notifications of clusters in your project, take the following s ### Step 2. Subscribe from TiDB Cloud +Alert notification subscriptions vary by product tier. + + + > **Tip:** > > The alert subscription is for all alerts in the current project. If you have multiple clusters in the project, you just need to subscribe once. @@ -44,15 +48,51 @@ To receive alert notifications of clusters in your project, take the following s 7. Click **Save** to complete the subscription. + + + + +> **Tip:** +> +> The alert subscription is for all alerts in the current cluster. If you have multiple clusters, you need to subscribe to each one individually. + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, click **Add Subscriber** in the upper-right corner. +4. Select **PagerDuty** from the **Subscriber Type** drop-down list. +5. Enter a name in the **Name** field and your PagerDuty integration key in the **Integration Key** field. +6. Click **Test Connection**. + + - If the test succeeds, the **Save** button is displayed. + - If the test fails, an error message is displayed. Follow the message to troubleshoot the issue and retry the connection. + +7. Click **Save** to complete the subscription. + + + Alternatively, you can also click **Subscribe** in the upper-right corner of the **Alert** page of the cluster. You will be directed to the **Alert Subscriber** page. If an alert condition remains unchanged, the alert sends notifications every three hours. ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications of clusters in your project, take the following steps: +If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. + + 1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner. 2. In the left navigation pane, click **Project Settings** > **Alert Subscription**. 3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. 4. Click **Unsubscribe** to confirm the unsubscription. + + + + + +1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target cluster using the combo box in the upper-left corner. +2. In the left navigation pane, click **Settings** > **Alert Subscription**. +3. On the **Alert Subscription** page, locate the row of your target subscriber to be deleted, and then click **...** > **Unsubscribe**. +4. Click **Unsubscribe** to confirm the unsubscription. + + + From e43042013e9a90ecc51f825d44ecb32a97b73a8a Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Fri, 30 Jan 2026 15:47:08 +0800 Subject: [PATCH 06/17] Update monitor-built-in-alerting.md --- tidb-cloud/monitor-built-in-alerting.md | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 0bef81dbf1ed0..306d48d94fbd9 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -11,7 +11,7 @@ This document describes how to do these operations and provides the TiDB Cloud b > **Note:** > -> Currently, the alert feature is only available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. ## View alerts @@ -58,7 +58,11 @@ The following table provides the TiDB Cloud built-in alert conditions and the co > > - While these alert conditions do not necessarily mean there is a problem, they are often early warning indicators of emerging issues. Therefore, taking the recommended action is advised. > - You can edit the thresholds of the alerts on the TiDB Cloud console. -> - Some alert rules are disabled by default. You can enable them as needed. +> - Some alert rules are disabled by default. You can enable them as needed. + +We provide distinct alert rules for each product tier, aligned with their respective feature sets. + + ### Resource usage alerts @@ -94,3 +98,12 @@ The following table provides the TiDB Cloud built-in alert conditions and the co | 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, you can 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, you can 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, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance. | + + + + +TBD. + + + + From ec4cc3e76ae78a8166d88bf684cc8dfe9c7fae82 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 2 Feb 2026 10:00:41 +0800 Subject: [PATCH 07/17] Apply suggestions from code review --- tidb-cloud/monitor-alert-email.md | 4 ++-- tidb-cloud/monitor-alert-flashduty.md | 4 ++-- tidb-cloud/monitor-alert-pagerduty.md | 4 ++-- tidb-cloud/monitor-alert-slack.md | 4 ++-- tidb-cloud/monitor-alert-zoom.md | 4 ++-- tidb-cloud/monitor-built-in-alerting.md | 2 +- 6 files changed, 11 insertions(+), 11 deletions(-) diff --git a/tidb-cloud/monitor-alert-email.md b/tidb-cloud/monitor-alert-email.md index 6f2481fcc2513..3a3da642688e9 100644 --- a/tidb-cloud/monitor-alert-email.md +++ b/tidb-cloud/monitor-alert-email.md @@ -17,7 +17,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via ## Subscribe to alert notifications -To receive alert notifications, take the following steps. The steps vary by product tier. +To receive alert notifications, take the following steps. The steps vary by cluster plans. @@ -65,7 +65,7 @@ If an alert condition remains unchanged, the alert sends email notifications eve ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. +If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. diff --git a/tidb-cloud/monitor-alert-flashduty.md b/tidb-cloud/monitor-alert-flashduty.md index 179d90a755527..6c080767f9a31 100644 --- a/tidb-cloud/monitor-alert-flashduty.md +++ b/tidb-cloud/monitor-alert-flashduty.md @@ -28,7 +28,7 @@ To receive alert notifications of clusters, take the following steps: ### Step 2. Subscribe from TiDB Cloud -Alert notification subscriptions vary by product tier. +Alert notification subscriptions vary by cluster plans. @@ -76,7 +76,7 @@ If an alert condition remains unchanged, the alert sends notifications every thr ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. +If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. diff --git a/tidb-cloud/monitor-alert-pagerduty.md b/tidb-cloud/monitor-alert-pagerduty.md index 264a1c7f8174d..d87856565fd99 100644 --- a/tidb-cloud/monitor-alert-pagerduty.md +++ b/tidb-cloud/monitor-alert-pagerduty.md @@ -28,7 +28,7 @@ To receive alert notifications, take the following steps: ### Step 2. Subscribe from TiDB Cloud -Alert notification subscriptions vary by product tier. +Alert notification subscriptions vary by cluster plans. @@ -76,7 +76,7 @@ If an alert condition remains unchanged, the alert sends notifications every thr ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. +If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. diff --git a/tidb-cloud/monitor-alert-slack.md b/tidb-cloud/monitor-alert-slack.md index 1cee6084d79f9..5821fafb527a9 100644 --- a/tidb-cloud/monitor-alert-slack.md +++ b/tidb-cloud/monitor-alert-slack.md @@ -32,7 +32,7 @@ You can see a new entry under the **Webhook URLs for Your Workspace** section in ### Step 2. Subscribe from TiDB Cloud -Alert notification subscriptions vary by product tier. +Alert notification subscriptions vary by cluster plans. @@ -80,7 +80,7 @@ If an alert condition remains unchanged, the alert sends notifications every thr ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. +If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. diff --git a/tidb-cloud/monitor-alert-zoom.md b/tidb-cloud/monitor-alert-zoom.md index 9bf676bac5499..03d060e4bf3b8 100644 --- a/tidb-cloud/monitor-alert-zoom.md +++ b/tidb-cloud/monitor-alert-zoom.md @@ -45,7 +45,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via ### Step 3. Subscribe from TiDB Cloud -Alert notification subscriptions vary by product tier. +Alert notification subscriptions vary by cluster plans. @@ -93,7 +93,7 @@ If an alert condition remains unchanged, the alert sends notifications every thr ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by product tier. +If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 306d48d94fbd9..a12b2b8cc62d3 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -60,7 +60,7 @@ The following table provides the TiDB Cloud built-in alert conditions and the co > - You can edit the thresholds of the alerts on the TiDB Cloud console. > - Some alert rules are disabled by default. You can enable them as needed. -We provide distinct alert rules for each product tier, aligned with their respective feature sets. +TiDB Cloud provides distinct alert rules for each cluster plan, aligned with their respective feature sets. From e3c85f396c7ff0792ab6b07e3d15090467a77bea Mon Sep 17 00:00:00 2001 From: huoyao1125 <90880576+huoyao1125@users.noreply.github.com> Date: Thu, 5 Feb 2026 18:38:00 +0800 Subject: [PATCH 08/17] Update monitor-built-in-alerting.md --- tidb-cloud/monitor-built-in-alerting.md | 37 +++++++++++++++++++++++-- 1 file changed, 34 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index a12b2b8cc62d3..7354928cf9298 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -96,13 +96,44 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | 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:
  • The overall traffic in the upstream has increased, causing the existing changefeed specification to be insufficient to handle it. If the traffic increase is temporary, the changefeed latency will automatically recover after the traffic returns to normal. If the traffic increase is continuous, you need to scale up the changefeed.
  • The downstream or network is abnormal. In this case, resolve this abnormality first.
  • Tables lack indexes if the downstream is RDS, which might cause low write performance and high latency. In this case, you need to add the necessary indexes to the upstream or downstream.
If the problem cannot be fixed from your side, you can 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, you can 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, you can 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, you can 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, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| + -TBD. +### Performance Overview alerts + +| Condition | Recommended Action | +|:--- |:--- | +| The Request Unit/s exceeded 80% of Max RCU | Suggested actions: +1. Check your traffic pattern in the RU metrics to determine if it's a gradual increase or a sharp spike. +2. If it's a gradual increase, verify if Query Duration has increased. If so, your current max RCU configuration is likely insufficient. +3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand. +If the problem cannot be fixed by your side, you can contact TiDB Cloud Support for further assistance.| +| QPS suddenly dropped by 80% | Suggested actions: +1. Check if it's caused by increasing query latency. +2. Check if your application is healthy. +If this drop is intentional, please ignore this alert. +If not, and you cannot identify the root cause, please contact Support immediately.| +| Query P99 latency exceeded 200 ms | Recommended Actions: +1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries. +2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern? +If you cannot identify the root cause, please contact Support immediately.| +| Query P95 latency exceeded 200 ms | Recommended Actions: +1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries. +2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern? +If you cannot identify the root cause, please contact Support immediately.| +| Request Error Rate exceeded 10% | Please check the recent errors and overall statement execution status for this cluster.| + +### Changefeed alerts + +| 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:
  • The overall traffic in the upstream has increased, causing the existing changefeed specification to be insufficient to handle it. If the traffic increase is temporary, the changefeed latency will automatically recover after the traffic returns to normal. If the traffic increase is continuous, you need to scale up the changefeed.
  • The downstream or network is abnormal. In this case, resolve this abnormality first.
  • Tables lack indexes if the downstream is RDS, which might cause low write performance and high latency. In this case, you need to add the necessary indexes to the upstream or downstream.
If the problem cannot be fixed from your side, you can 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, you can 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, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| From 67605bb4eff877d71ada578f67d318087a2a53b2 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 6 Feb 2026 15:28:55 +0800 Subject: [PATCH 09/17] Apply suggestions from code review --- tidb-cloud/monitor-alert-pagerduty.md | 2 +- tidb-cloud/monitor-alert-slack.md | 2 +- tidb-cloud/monitor-alert-zoom.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/monitor-alert-pagerduty.md b/tidb-cloud/monitor-alert-pagerduty.md index d87856565fd99..4b5ed7334e9b3 100644 --- a/tidb-cloud/monitor-alert-pagerduty.md +++ b/tidb-cloud/monitor-alert-pagerduty.md @@ -76,7 +76,7 @@ If an alert condition remains unchanged, the alert sends notifications every thr ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. +If you no longer want to receive alert notifications, take the following steps. The steps vary by cluster plans. diff --git a/tidb-cloud/monitor-alert-slack.md b/tidb-cloud/monitor-alert-slack.md index 5821fafb527a9..00bd1a5848970 100644 --- a/tidb-cloud/monitor-alert-slack.md +++ b/tidb-cloud/monitor-alert-slack.md @@ -80,7 +80,7 @@ If an alert condition remains unchanged, the alert sends notifications every thr ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. +If you no longer want to receive alert notifications, take the following steps. The steps vary by cluster plans. diff --git a/tidb-cloud/monitor-alert-zoom.md b/tidb-cloud/monitor-alert-zoom.md index 03d060e4bf3b8..0899d28290bb8 100644 --- a/tidb-cloud/monitor-alert-zoom.md +++ b/tidb-cloud/monitor-alert-zoom.md @@ -93,7 +93,7 @@ If an alert condition remains unchanged, the alert sends notifications every thr ## Unsubscribe from alert notifications -If you no longer want to receive alert notifications, please take the following steps. The steps vary by cluster plans. +If you no longer want to receive alert notifications, take the following steps. The steps vary by cluster plans. From 84aad370fa1404f557c4e87d9a18876811acd21d Mon Sep 17 00:00:00 2001 From: houfaxin Date: Fri, 6 Feb 2026 15:41:20 +0800 Subject: [PATCH 10/17] refine wording --- tidb-cloud/monitor-built-in-alerting.md | 26 +++++-------------------- 1 file changed, 5 insertions(+), 21 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 7354928cf9298..3fee11b52f264 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -107,25 +107,11 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | Condition | Recommended Action | |:--- |:--- | -| The Request Unit/s exceeded 80% of Max RCU | Suggested actions: -1. Check your traffic pattern in the RU metrics to determine if it's a gradual increase or a sharp spike. -2. If it's a gradual increase, verify if Query Duration has increased. If so, your current max RCU configuration is likely insufficient. -3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand. -If the problem cannot be fixed by your side, you can contact TiDB Cloud Support for further assistance.| -| QPS suddenly dropped by 80% | Suggested actions: -1. Check if it's caused by increasing query latency. -2. Check if your application is healthy. -If this drop is intentional, please ignore this alert. -If not, and you cannot identify the root cause, please contact Support immediately.| -| Query P99 latency exceeded 200 ms | Recommended Actions: -1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries. -2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern? -If you cannot identify the root cause, please contact Support immediately.| -| Query P95 latency exceeded 200 ms | Recommended Actions: -1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries. -2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern? -If you cannot identify the root cause, please contact Support immediately.| -| Request Error Rate exceeded 10% | Please check the recent errors and overall statement execution status for this cluster.| +| The Request Unit/s exceeded 80% of Max RCU | Suggested actions:
  • 1. Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.
  • 2. If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.
  • 3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.

If the problem cannot be fixed by your side, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| +| QPS suddenly dropped by 80% | Suggested actions:
  • 1. Check if it's caused by increasing query latency.
  • 2. Check if your application is healthy. If this drop is intentional, ignore this alert. If this drop is not intentional and you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.
| +| Query P99 latency exceeded 200 ms | Recommended Actions:
  • 1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries.
  • 2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| +| Query P95 latency exceeded 200 ms | Recommended Actions:
  • 1. Investigate slow queries: go to the Slow Query page and filter by the recent time range to find newly appeared or slower-running queries.
  • 2. Review recent changes: was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| +| Request Error Rate exceeded 10% | Check the recent errors and overall statement execution status for this cluster.| ### Changefeed alerts @@ -136,5 +122,3 @@ If you cannot identify the root cause, please contact Support immediately.| | 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, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| - - From a1bcf1850d4950f5d78e977aa5aaee6f03c4323d Mon Sep 17 00:00:00 2001 From: houfaxin Date: Fri, 6 Feb 2026 15:42:49 +0800 Subject: [PATCH 11/17] 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 3fee11b52f264..a96605fc94ff7 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -107,7 +107,7 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | Condition | Recommended Action | |:--- |:--- | -| The Request Unit/s exceeded 80% of Max RCU | Suggested actions:
  • 1. Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.
  • 2. If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.
  • 3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.

If the problem cannot be fixed by your side, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| +| The Request Unit/s exceeded 80% of Max RCU | Suggested actions:
  • 1. Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.
  • 2. If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.
  • 3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.

If the problem cannot be fixed by your side, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| | QPS suddenly dropped by 80% | Suggested actions:
  • 1. Check if it's caused by increasing query latency.
  • 2. Check if your application is healthy. If this drop is intentional, ignore this alert. If this drop is not intentional and you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.
| | Query P99 latency exceeded 200 ms | Recommended Actions:
  • 1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries.
  • 2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Query P95 latency exceeded 200 ms | Recommended Actions:
  • 1. Investigate slow queries: go to the Slow Query page and filter by the recent time range to find newly appeared or slower-running queries.
  • 2. Review recent changes: was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| From 1662e7371d460c1944e2e88c54d04225e3e99335 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 9 Feb 2026 09:41:59 +0800 Subject: [PATCH 12/17] Update monitor-built-in-alerting.md --- tidb-cloud/monitor-built-in-alerting.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index a96605fc94ff7..8c347b4411470 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -107,10 +107,10 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | Condition | Recommended Action | |:--- |:--- | -| The Request Unit/s exceeded 80% of Max RCU | Suggested actions:
  • 1. Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.
  • 2. If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.
  • 3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.

If the problem cannot be fixed by your side, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| -| QPS suddenly dropped by 80% | Suggested actions:
  • 1. Check if it's caused by increasing query latency.
  • 2. Check if your application is healthy. If this drop is intentional, ignore this alert. If this drop is not intentional and you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.
| -| Query P99 latency exceeded 200 ms | Recommended Actions:
  • 1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries.
  • 2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| -| Query P95 latency exceeded 200 ms | Recommended Actions:
  • 1. Investigate slow queries: go to the Slow Query page and filter by the recent time range to find newly appeared or slower-running queries.
  • 2. Review recent changes: was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| +| The Request Unit/s exceeded 80% of Max RCU | Suggested actions:
  1. Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.
  2. If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.
  3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.

If the problem cannot be fixed by your side, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| +| QPS suddenly dropped by 80% | Suggested actions:
  1. Check if it's caused by increasing query latency.
  2. Check if your application is healthy. If this drop is intentional, ignore this alert. If this drop is not intentional and you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.
| +| Query P99 latency exceeded 200 ms | Recommended Actions:
  1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries.
  2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| +| Query P95 latency exceeded 200 ms | Recommended Actions:
  1. Investigate slow queries: go to the Slow Query page and filter by the recent time range to find newly appeared or slower-running queries.
  2. Review recent changes: was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Request Error Rate exceeded 10% | Check the recent errors and overall statement execution status for this cluster.| ### Changefeed alerts From aad118cad3c399b81df888d8018130dde0f7c8ca Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 9 Feb 2026 09:44:08 +0800 Subject: [PATCH 13/17] Update monitor-built-in-alerting.md --- tidb-cloud/monitor-built-in-alerting.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 8c347b4411470..bc7bcc8fcef73 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -95,9 +95,9 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | 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:
  • The overall traffic in the upstream has increased, causing the existing changefeed specification to be insufficient to handle it. If the traffic increase is temporary, the changefeed latency will automatically recover after the traffic returns to normal. If the traffic increase is continuous, you need to scale up the changefeed.
  • The downstream or network is abnormal. In this case, resolve this abnormality first.
  • Tables lack indexes if the downstream is RDS, which might cause low write performance and high latency. In this case, you need to add the necessary indexes to the upstream or downstream.
If the problem cannot be fixed from your side, you can 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, you can 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, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| +| 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:
  • The overall traffic in the upstream has increased, causing the existing changefeed specification to be insufficient to handle it. If the traffic increase is temporary, the changefeed latency will automatically recover after the traffic returns to normal. If the traffic increase is continuous, you need to scale up the changefeed.
  • The downstream or network is abnormal. In this case, resolve this abnormality first.
  • Tables lack indexes if the downstream is RDS, which might cause low write performance and high latency. In this case, you need to add the necessary indexes to the upstream or downstream.
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.| @@ -107,7 +107,7 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | Condition | Recommended Action | |:--- |:--- | -| The Request Unit/s exceeded 80% of Max RCU | Suggested actions:
  1. Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.
  2. If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.
  3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.

If the problem cannot be fixed by your side, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| +| The Request Unit/s exceeded 80% of Max RCU | Suggested actions:
  1. Check your traffic pattern in the RU metrics to determine if it is a gradual increase or a sharp spike.
  2. If it is a gradual increase, verify if Query Duration has increased. If yes, your current max RCU configuration is likely insufficient.
  3. Scale up your capacity by manually increasing the max RCU in the TiDB Cloud console to meet demand.

If the problem cannot be fixed by your side, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| | QPS suddenly dropped by 80% | Suggested actions:
  1. Check if it's caused by increasing query latency.
  2. Check if your application is healthy. If this drop is intentional, ignore this alert. If this drop is not intentional and you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.
| | Query P99 latency exceeded 200 ms | Recommended Actions:
  1. Investigate Slow Queries: Go to Slow Query page. Filter by the recent time range to find newly appeared or slower-running queries.
  2. Review Recent Changes: Was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Query P95 latency exceeded 200 ms | Recommended Actions:
  1. Investigate slow queries: go to the Slow Query page and filter by the recent time range to find newly appeared or slower-running queries.
  2. Review recent changes: was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| From 0203c6f0df0a6dff7b6a0b23fee958d4ffd97121 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 9 Feb 2026 09:45:19 +0800 Subject: [PATCH 14/17] Update 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 bc7bcc8fcef73..0557a88b6d7ce 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -117,8 +117,8 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | 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:
  • The overall traffic in the upstream has increased, causing the existing changefeed specification to be insufficient to handle it. If the traffic increase is temporary, the changefeed latency will automatically recover after the traffic returns to normal. If the traffic increase is continuous, you need to scale up the changefeed.
  • The downstream or network is abnormal. In this case, resolve this abnormality first.
  • Tables lack indexes if the downstream is RDS, which might cause low write performance and high latency. In this case, you need to add the necessary indexes to the upstream or downstream.
If the problem cannot be fixed from your side, you can 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, you can 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, you can contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for further assistance.| +| 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:
  • The overall traffic in the upstream has increased, causing the existing changefeed specification to be insufficient to handle it. If the traffic increase is temporary, the changefeed latency will automatically recover after the traffic returns to normal. If the traffic increase is continuous, you need to scale up the changefeed.
  • The downstream or network is abnormal. In this case, resolve this abnormality first.
  • Tables lack indexes if the downstream is RDS, which might cause low write performance and high latency. In this case, you need to add the necessary indexes to the upstream or downstream.
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.| From 3fcc6464e20f4e21eee9d2d79c38482ae1acaf1a Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 9 Feb 2026 10:59:19 +0800 Subject: [PATCH 15/17] fix error --- tidb-cloud/monitor-alert-pagerduty.md | 1 - tidb-cloud/monitor-alert-slack.md | 1 - tidb-cloud/monitor-built-in-alerting.md | 4 ++-- 3 files changed, 2 insertions(+), 4 deletions(-) diff --git a/tidb-cloud/monitor-alert-pagerduty.md b/tidb-cloud/monitor-alert-pagerduty.md index 4b5ed7334e9b3..ecd891a8122dc 100644 --- a/tidb-cloud/monitor-alert-pagerduty.md +++ b/tidb-cloud/monitor-alert-pagerduty.md @@ -95,4 +95,3 @@ If you no longer want to receive alert notifications, take the following steps. 4. Click **Unsubscribe** to confirm the unsubscription. - diff --git a/tidb-cloud/monitor-alert-slack.md b/tidb-cloud/monitor-alert-slack.md index 00bd1a5848970..6d08ad30870be 100644 --- a/tidb-cloud/monitor-alert-slack.md +++ b/tidb-cloud/monitor-alert-slack.md @@ -7,7 +7,6 @@ summary: Learn how to monitor your TiDB cluster by getting alert notifications v TiDB Cloud provides you with an easy way to subscribe to alert notifications via Slack, [email](/tidb-cloud/monitor-alert-email.md), [Zoom](/tidb-cloud/monitor-alert-zoom.md), [Flashduty](/tidb-cloud/monitor-alert-flashduty.md), and [PagerDuty](/tidb-cloud/monitor-alert-pagerduty.md). This document describes how to subscribe to alert notifications via Slack. - > **Note:** > > Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 0557a88b6d7ce..185d935fa9059 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -91,7 +91,7 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | Data migration job has been paused for more than 6 hours during incremental migration | Data migration job has been paused for more than 6 hours during data incremental migration. The binlog in the upstream database might be purged (depending on your database binlog purge strategy) and might cause incremental migration to fail. See [Troubleshoot data migration](/tidb-cloud/tidb-cloud-dm-precheck-and-troubleshooting.md#migration-errors-and-solutions) for help. | | Replication lag is larger than 10 minutes and still increasing for more than 20 minutes | See [Troubleshoot data migration](/tidb-cloud/tidb-cloud-dm-precheck-and-troubleshooting.md#migration-errors-and-solutions) for help. | -### Changefeed alerts +### Changefeed alerts for {{{ .dedicated }}} | Condition | Recommended Action | |:--------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -113,7 +113,7 @@ TiDB Cloud provides distinct alert rules for each cluster plan, aligned with the | Query P95 latency exceeded 200 ms | Recommended Actions:
  1. Investigate slow queries: go to the Slow Query page and filter by the recent time range to find newly appeared or slower-running queries.
  2. Review recent changes: was there a recent application deployment, schema change, or data import job that could explain the change in traffic pattern?

If you cannot identify the root cause, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) immediately.| | Request Error Rate exceeded 10% | Check the recent errors and overall statement execution status for this cluster.| -### Changefeed alerts +### Changefeed alerts for {{{ .essential }}} | Condition | Recommended Action | |:--------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| From 5ed3dee8302596d94a3e18aaa72e4601abf2eb21 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 9 Feb 2026 11:04:26 +0800 Subject: [PATCH 16/17] update essential link --- tidb-cloud/monitor-alert-email.md | 2 +- tidb-cloud/monitor-alert-flashduty.md | 2 +- tidb-cloud/monitor-alert-pagerduty.md | 2 +- tidb-cloud/monitor-alert-slack.md | 2 +- tidb-cloud/monitor-alert-zoom.md | 2 +- tidb-cloud/monitor-built-in-alerting.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/monitor-alert-email.md b/tidb-cloud/monitor-alert-email.md index 3a3da642688e9..115fda0f7e4dd 100644 --- a/tidb-cloud/monitor-alert-email.md +++ b/tidb-cloud/monitor-alert-email.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-flashduty.md b/tidb-cloud/monitor-alert-flashduty.md index 6c080767f9a31..49d7d564deccf 100644 --- a/tidb-cloud/monitor-alert-flashduty.md +++ b/tidb-cloud/monitor-alert-flashduty.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-pagerduty.md b/tidb-cloud/monitor-alert-pagerduty.md index ecd891a8122dc..ceda60aca9803 100644 --- a/tidb-cloud/monitor-alert-pagerduty.md +++ b/tidb-cloud/monitor-alert-pagerduty.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-slack.md b/tidb-cloud/monitor-alert-slack.md index 6d08ad30870be..07a44b226c39f 100644 --- a/tidb-cloud/monitor-alert-slack.md +++ b/tidb-cloud/monitor-alert-slack.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-zoom.md b/tidb-cloud/monitor-alert-zoom.md index 0899d28290bb8..cade8c302a0a9 100644 --- a/tidb-cloud/monitor-alert-zoom.md +++ b/tidb-cloud/monitor-alert-zoom.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 185d935fa9059..39b1e7e54b6a0 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -11,7 +11,7 @@ This document describes how to do these operations and provides the TiDB Cloud b > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#tidb-cloud-essetial) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. ## View alerts From 4ddfa6061460fda59044901ebc3e27cbfc95385f Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 9 Feb 2026 11:12:32 +0800 Subject: [PATCH 17/17] fix essential links --- tidb-cloud/monitor-alert-email.md | 2 +- tidb-cloud/monitor-alert-flashduty.md | 2 +- tidb-cloud/monitor-alert-pagerduty.md | 2 +- tidb-cloud/monitor-alert-slack.md | 2 +- tidb-cloud/monitor-alert-zoom.md | 2 +- tidb-cloud/monitor-built-in-alerting.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/monitor-alert-email.md b/tidb-cloud/monitor-alert-email.md index 115fda0f7e4dd..78a5f5a6c1e55 100644 --- a/tidb-cloud/monitor-alert-email.md +++ b/tidb-cloud/monitor-alert-email.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-flashduty.md b/tidb-cloud/monitor-alert-flashduty.md index 49d7d564deccf..805fe955f2903 100644 --- a/tidb-cloud/monitor-alert-flashduty.md +++ b/tidb-cloud/monitor-alert-flashduty.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-pagerduty.md b/tidb-cloud/monitor-alert-pagerduty.md index ceda60aca9803..05e50252dd349 100644 --- a/tidb-cloud/monitor-alert-pagerduty.md +++ b/tidb-cloud/monitor-alert-pagerduty.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-slack.md b/tidb-cloud/monitor-alert-slack.md index 07a44b226c39f..306cd99b33316 100644 --- a/tidb-cloud/monitor-alert-slack.md +++ b/tidb-cloud/monitor-alert-slack.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-alert-zoom.md b/tidb-cloud/monitor-alert-zoom.md index cade8c302a0a9..88a1a7ac8a633 100644 --- a/tidb-cloud/monitor-alert-zoom.md +++ b/tidb-cloud/monitor-alert-zoom.md @@ -9,7 +9,7 @@ TiDB Cloud provides you with an easy way to subscribe to alert notifications via > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential) clusters. ## Prerequisites diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 39b1e7e54b6a0..a47399922324c 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -11,7 +11,7 @@ This document describes how to do these operations and provides the TiDB Cloud b > **Note:** > -> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#-essential--essential) clusters. +> Currently, alert subscription is available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) and [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential) clusters. ## View alerts