diff --git a/TOC-tidb-cloud-essential.md b/TOC-tidb-cloud-essential.md index 0532f052e2c31..83f2a691ffb4e 100644 --- a/TOC-tidb-cloud-essential.md +++ b/TOC-tidb-cloud-essential.md @@ -158,6 +158,11 @@ - Monitor and Alert - [Overview](/tidb-cloud/monitor-tidb-cluster.md) - [Built-in Metrics](/tidb-cloud/built-in-monitoring.md) + - [Built-in Alerting](/tidb-cloud/monitor-built-in-alerting.md) + - Subscribe to Alert Notifications + - [Subscribe via Email](/tidb-cloud/monitor-alert-email.md) + - [Subscribe via Slack](/tidb-cloud/monitor-alert-slack.md) + - [Subscribe via Zoom](/tidb-cloud/monitor-alert-zoom.md) - [Cluster Events](/tidb-cloud/tidb-cloud-events.md) - Tune Performance - [Overview](/tidb-cloud/tidb-cloud-tune-performance-overview.md) @@ -688,6 +693,11 @@ - [Connected Care Details](/tidb-cloud/connected-care-detail.md) - Connected Care Support Service Features - [Connected: AI Chat in IM](/tidb-cloud/connected-ai-chat-in-im.md) + - Connected: IM Subscription for TiDB Cloud Alerts + - [Subscribe via Slack](/tidb-cloud/monitor-alert-slack.md) + - [Subscribe via Zoom](/tidb-cloud/monitor-alert-zoom.md) + - [Subscribe via Flashduty](/tidb-cloud/monitor-alert-flashduty.md) + - [Subscribe via PagerDuty](/tidb-cloud/monitor-alert-pagerduty.md) - Connected: IM Ticket Creation and Update Subscription - [Create Tickets and Subscribe to Ticket Updates via Slack](/tidb-cloud/connected-slack-ticket-creation.md) - [Create Tickets and Subscribe to Ticket Updates via Lark](/tidb-cloud/connected-lark-ticket-creation.md) diff --git a/tidb-cloud/monitor-alert-email.md b/tidb-cloud/monitor-alert-email.md index 0376a0b8cc03e..c12cd1257408a 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 Essential](/tidb-cloud/select-cluster-tier.md#essential) and [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) 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 cluster plan. + + + > **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 cluster 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 cluster plan. + + 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. + + diff --git a/tidb-cloud/monitor-alert-flashduty.md b/tidb-cloud/monitor-alert-flashduty.md index e580cc130f8ba..7792dcb6e39dc 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 Essential](/tidb-cloud/select-cluster-tier.md#essential) and [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) 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 cluster plan. + + + > **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 cluster 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, take the following steps. The steps vary by cluster plan. + + 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. + + diff --git a/tidb-cloud/monitor-alert-pagerduty.md b/tidb-cloud/monitor-alert-pagerduty.md index b049b3be0ee3f..4cdb3628c25eb 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 Essential](/tidb-cloud/select-cluster-tier.md#essential) and [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) 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 cluster plan. + + + > **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 cluster 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 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, take the following steps. The steps vary by cluster plan. + + 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. + + diff --git a/tidb-cloud/monitor-alert-slack.md b/tidb-cloud/monitor-alert-slack.md index dc38b6e5800dc..b2c748f26d0a0 100644 --- a/tidb-cloud/monitor-alert-slack.md +++ b/tidb-cloud/monitor-alert-slack.md @@ -7,13 +7,9 @@ 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 Essential](/tidb-cloud/select-cluster-tier.md#essential) and [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters. ## Prerequisites @@ -35,6 +31,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 cluster plan. + + + > **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 +51,50 @@ You can see a new entry under the **Webhook URLs for Your Workspace** section in 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 cluster 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 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, take the following steps. The steps vary by cluster plan. + + 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. + + diff --git a/tidb-cloud/monitor-alert-zoom.md b/tidb-cloud/monitor-alert-zoom.md index 21755ea0aea71..46966a1274c46 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 Essential](/tidb-cloud/select-cluster-tier.md#essential) and [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) 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 cluster plan. + + + > **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 cluster 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, take the following steps. The steps vary by cluster plan. + + 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. + + diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 0bef81dbf1ed0..29c04d1eb3192 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 Essential](/tidb-cloud/select-cluster-tier.md#essential) and [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) 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. + +TiDB Cloud provides different alert rules for each cluster plan, based on the features available in that plan. + + ### Resource usage alerts @@ -87,10 +91,34 @@ The following table provides the TiDB Cloud built-in alert conditions and the co | 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 | |:--------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 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. | +| 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 + +| 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.| + +### Changefeed alerts for {{{ .essential }}} + +| 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.| + +