diff --git a/TOC-tidb-cloud.md b/TOC-tidb-cloud.md index 1bb3949221c31..558c02489049a 100644 --- a/TOC-tidb-cloud.md +++ b/TOC-tidb-cloud.md @@ -122,7 +122,7 @@ - [Built-in Metrics](/tidb-cloud/built-in-monitoring.md) - [Built-in Alerting](/tidb-cloud/monitor-built-in-alerting.md) - [Cluster Events](/tidb-cloud/tidb-cloud-events.md) - - [Third-Party Metrics Integrations](/tidb-cloud/third-party-monitoring-integrations.md) + - [Third-Party Metrics Integrations (Beta)](/tidb-cloud/third-party-monitoring-integrations.md) - Tune Performance - [Overview](/tidb-cloud/tidb-cloud-tune-performance-overview.md) - Analyze Performance diff --git a/br/backup-and-restore-storages.md b/br/backup-and-restore-storages.md index 23c9fa39952ea..994ef02cbd6f4 100644 --- a/br/backup-and-restore-storages.md +++ b/br/backup-and-restore-storages.md @@ -92,7 +92,7 @@ This section provides some URL examples by using `external` as the `host` parame **Back up snapshot data to Amazon S3** ```shell -./br restore full -u "${PD_IP}:2379" \ +./br backup full -u "${PD_IP}:2379" \ --storage "s3://external/backup-20220915?access-key=${access-key}&secret-access-key=${secret-access-key}" ``` diff --git a/develop/dev-guide-aws-appflow-integration.md b/develop/dev-guide-aws-appflow-integration.md index 1b2ff2a604b4c..061ca285b3be4 100644 --- a/develop/dev-guide-aws-appflow-integration.md +++ b/develop/dev-guide-aws-appflow-integration.md @@ -244,5 +244,4 @@ test> SELECT * FROM sf_account; - If anything goes wrong, you can navigate to the [CloudWatch](https://console.aws.amazon.com/cloudwatch/home) page on the AWS Management Console to get logs. - The steps in this document are based on [Building custom connectors using the Amazon AppFlow Custom Connector SDK](https://aws.amazon.com/blogs/compute/building-custom-connectors-using-the-amazon-appflow-custom-connector-sdk/). -- [TiDB Serverless](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-serverless-beta) is **NOT** a production environment. - To prevent excessive length, the examples in this document only show the `Insert` strategy, but `Update` and `Upsert` strategies are also tested and can be used. \ No newline at end of file diff --git a/develop/dev-guide-build-cluster-in-cloud.md b/develop/dev-guide-build-cluster-in-cloud.md index 1c7fd0dceee71..aa17c6eb40907 100644 --- a/develop/dev-guide-build-cluster-in-cloud.md +++ b/develop/dev-guide-build-cluster-in-cloud.md @@ -46,7 +46,7 @@ This document walks you through the quickest way to get started with TiDB Cloud. > **Note:** > -> For [TiDB Serverless clusters](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-serverless-beta), when you connect to your cluster, you must include the prefix for your cluster in the user name and wrap the name with quotation marks. For more information, see [User name prefix](https://docs.pingcap.com/tidbcloud/select-cluster-tier#user-name-prefix). +> For [TiDB Serverless clusters](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-serverless), when you connect to your cluster, you must include the prefix for your cluster in the user name and wrap the name with quotation marks. For more information, see [User name prefix](https://docs.pingcap.com/tidbcloud/select-cluster-tier#user-name-prefix). @@ -54,7 +54,7 @@ This document walks you through the quickest way to get started with TiDB Cloud. > **Note:** > -> For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta), when you connect to your cluster, you must include the prefix for your cluster in the user name and wrap the name with quotation marks. For more information, see [User name prefix](/tidb-cloud/select-cluster-tier.md#user-name-prefix). +> For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless), when you connect to your cluster, you must include the prefix for your cluster in the user name and wrap the name with quotation marks. For more information, see [User name prefix](/tidb-cloud/select-cluster-tier.md#user-name-prefix). diff --git a/develop/dev-guide-third-party-support.md b/develop/dev-guide-third-party-support.md index ee073c871f489..6fbfdea0d209c 100644 --- a/develop/dev-guide-third-party-support.md +++ b/develop/dev-guide-third-party-support.md @@ -251,8 +251,8 @@ If you encounter problems when connecting to TiDB using the tools listed in this Python Django - v4.0.5 - Compatible + v4.1 + Full django-tidb N/A diff --git a/information-schema/information-schema-slow-query.md b/information-schema/information-schema-slow-query.md index d47b6e5f1ff41..89d2d2ab273f4 100644 --- a/information-schema/information-schema-slow-query.md +++ b/information-schema/information-schema-slow-query.md @@ -11,7 +11,7 @@ The `SLOW_QUERY` table provides the slow query information of the current node, > **Note:** > -> The `SLOW_QUERY` table is unavailable for [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +> The `SLOW_QUERY` table is unavailable for [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless). diff --git a/sql-statements/sql-statement-flashback-to-timestamp.md b/sql-statements/sql-statement-flashback-to-timestamp.md index 4a3c733395a1d..fc13259a56de9 100644 --- a/sql-statements/sql-statement-flashback-to-timestamp.md +++ b/sql-statements/sql-statement-flashback-to-timestamp.md @@ -11,7 +11,7 @@ TiDB v6.4.0 introduces the `FLASHBACK CLUSTER TO TIMESTAMP` syntax. You can use > **Warning:** > -> The `FLASHBACK CLUSTER TO TIMESTAMP` syntax is not applicable to [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. Do not execute this statement on TiDB Serverless clusters to avoid unexpected results. +> The `FLASHBACK CLUSTER TO TIMESTAMP` syntax is not applicable to [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. Do not execute this statement on TiDB Serverless clusters to avoid unexpected results. diff --git a/statement-summary-tables.md b/statement-summary-tables.md index dec45e63e3fac..4ed78a6192327 100644 --- a/statement-summary-tables.md +++ b/statement-summary-tables.md @@ -19,7 +19,7 @@ Therefore, starting from v4.0.0-rc.1, TiDB provides system tables in `informatio > **Note:** > -> The following tables are unavailable for [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta): `statements_summary`, `statements_summary_history`, `cluster_statements_summary`, and `cluster_statements_summary_history`. +> The following tables are unavailable for [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless): `statements_summary`, `statements_summary_history`, `cluster_statements_summary`, and `cluster_statements_summary_history`. diff --git a/system-variables.md b/system-variables.md index f5b0858db1f8e..25b478766d744 100644 --- a/system-variables.md +++ b/system-variables.md @@ -1116,7 +1116,7 @@ MPP is a distributed computing framework provided by the TiFlash engine, which a > **Note:** > -> To improve the speed for index creation using this variable, make sure that your TiDB cluster is hosted on AWS and your TiDB node size is at least 8 vCPU. For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters, this feature is unavailable. +> To improve the speed for index creation using this variable, make sure that your TiDB cluster is hosted on AWS and your TiDB node size is at least 8 vCPU. For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters, this feature is unavailable. diff --git a/tidb-cloud/backup-and-restore-serverless.md b/tidb-cloud/backup-and-restore-serverless.md index f168ba72ffb68..ba0a494131f86 100644 --- a/tidb-cloud/backup-and-restore-serverless.md +++ b/tidb-cloud/backup-and-restore-serverless.md @@ -16,7 +16,6 @@ This document describes how to back up and restore your TiDB Serverless cluster - It is important to note that TiDB Serverless clusters only support in-place restoring from backups. When a restore is performed, tables in the `mysql` schema are also impacted. Hence, any changes made to user credentials and permissions or system variables will be rolled back to the state when the backup was taken. - Manual backup is not yet supported. -- PITR (Point-in-time Recovery) is not yet supported. - The cluster will be unavailable during the restore process, and existing connections will be terminated. You can establish new connections once the restore is complete. - If any TiFlash replica is enabled, the replica will be unavailable for a while after the restore because data needs to be rebuilt in TiFlash. @@ -56,9 +55,35 @@ TiDB Serverless only supports in-place restoration. To restore your TiDB Serverl 1. Navigate to the **Backup** page of a cluster. -2. Click **Restore**. This will open the **Restore** window. +2. Click **Restore**. The setting window displays. - 1. Choose a backup from the **Backup Time** drop-down list. - 2. Click **Confirm** to begin the restoration process. +3. In **Restore Mode**, you can choose to restore from a specific backup or any point in time. - After initiating the restore process, the cluster status changes to **Restoring**. The cluster will be unavailable during the restore process and existing connections will be terminated. Once the restore process completes successfully, you can access the cluster as usual. \ No newline at end of file + +
+ + To restore from a selected backup snapshot, take the following steps: + + 1. Click **Basic Snapshot Restore**. + 2. Select the backup snapshot you want to restore to. + +
+
+ + This feature lets you restore a cluster to a specific state from any time within the last 90 days. + + > **Note:** + > + > The **Point-in-Time Restore** feature is currently in beta. + + To restore from a specific point in time, take the following steps: + + 1. Click **Point-in-Time Restore**. + 2. Select the date and time you want to restore to. + +
+ + +4. Click **Restore** to begin the restoration process. + + After initiating the restore process, the cluster status changes to **Restoring**. The cluster will be unavailable during the restore process and existing connections will be terminated. Once the restore process completes successfully, you can access the cluster as usual. diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index 7dee1619fb13e..8bf5f6daf4f06 100644 --- a/tidb-cloud/backup-and-restore.md +++ b/tidb-cloud/backup-and-restore.md @@ -165,12 +165,8 @@ To restore your TiDB Dedicated cluster data from a backup to a new cluster, take To restore a deleted cluster from recycle bin, take the following steps: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Recycle Bin**. - - If you only have one project, click **Admin** > **Recycle Bin**. - -3. Locate the cluster you want to restore, and then click **Backups** in the **Action** column. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Recycle Bin** in the left navigation pane, locate the cluster you want to restore, and then click **Backups** in the **Action** column. 4. Locate your desired backup time, and then click **Restore** in the **Action** column. 5. In the **Restore** window, make the following changes if necessary: diff --git a/tidb-cloud/built-in-monitoring.md b/tidb-cloud/built-in-monitoring.md index 4c3394f1131d2..fc18d7d7f1903 100644 --- a/tidb-cloud/built-in-monitoring.md +++ b/tidb-cloud/built-in-monitoring.md @@ -15,7 +15,7 @@ To view the metrics on the Metrics page, take the following steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of the target cluster. The cluster overview page is displayed. 3. Click **Metrics** in the left navigation pane. diff --git a/tidb-cloud/changefeed-overview.md b/tidb-cloud/changefeed-overview.md index 6e4f0619813fe..b81f74f4166dd 100644 --- a/tidb-cloud/changefeed-overview.md +++ b/tidb-cloud/changefeed-overview.md @@ -11,7 +11,7 @@ TiDB Cloud changefeed helps you stream data from TiDB Cloud to other data servic > > - To use the changefeed feature, make sure that your TiDB Dedicated cluster version is v6.4.0 or later. > - Currently, TiDB Cloud only allows up to 5 changefeeds per cluster. -> - For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta), the changefeed feature is unavailable. +> - For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless), the changefeed feature is unavailable. To access the changefeed feature, navigate to the cluster overview page of your TiDB cluster, and then click **Changefeed** in the left navigation pane. The changefeed page is displayed. diff --git a/tidb-cloud/changefeed-sink-to-apache-kafka.md b/tidb-cloud/changefeed-sink-to-apache-kafka.md index 1375a453819a5..57d528d9be980 100644 --- a/tidb-cloud/changefeed-sink-to-apache-kafka.md +++ b/tidb-cloud/changefeed-sink-to-apache-kafka.md @@ -10,7 +10,7 @@ This document describes how to create a changefeed to stream data from TiDB Clou > **Note:** > > - Currently, Kafka sink is in **beta**. To use the changefeed feature, make sure that your TiDB Dedicated cluster version is v6.4.0 or later and the TiKV node size is at least 8 vCPU and 16 GiB. -> - For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta), the changefeed feature is unavailable. +> - For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless), the changefeed feature is unavailable. ## Restrictions diff --git a/tidb-cloud/changefeed-sink-to-cloud-storage.md b/tidb-cloud/changefeed-sink-to-cloud-storage.md index 5ad69e5963106..9d3673a8dd737 100644 --- a/tidb-cloud/changefeed-sink-to-cloud-storage.md +++ b/tidb-cloud/changefeed-sink-to-cloud-storage.md @@ -10,7 +10,7 @@ This document describes how to create a changefeed to stream data from TiDB Clou > **Note:** > > - To stream data to cloud storage, make sure that your TiDB cluster version is v7.1.0 or later. To upgrade your TiDB Dedicated cluster to v7.1.0 or later, [contact TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md). -> - For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters, the changefeed feature is unavailable. +> - For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters, the changefeed feature is unavailable. ## Restrictions diff --git a/tidb-cloud/changefeed-sink-to-mysql.md b/tidb-cloud/changefeed-sink-to-mysql.md index ff1b1d4c21f84..0c42281c65827 100644 --- a/tidb-cloud/changefeed-sink-to-mysql.md +++ b/tidb-cloud/changefeed-sink-to-mysql.md @@ -11,7 +11,7 @@ This document describes how to stream data from TiDB Cloud to MySQL using the ** > > - To use the changefeed feature, make sure that your TiDB Dedicated cluster version is v6.4.0 or later and the TiKV node size is at least 8 vCPU and 16 GiB. > - Currently, TiDB Cloud only allows up to 5 changefeeds per cluster. -> - For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta), the changefeed feature is unavailable. +> - For [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless), the changefeed feature is unavailable. ## Restrictions diff --git a/tidb-cloud/config-s3-and-gcs-access.md b/tidb-cloud/config-s3-and-gcs-access.md index 6c539d680739d..8e68ee7c2cef6 100644 --- a/tidb-cloud/config-s3-and-gcs-access.md +++ b/tidb-cloud/config-s3-and-gcs-access.md @@ -49,7 +49,7 @@ Configure the bucket access for TiDB Cloud and get the Role ARN as follows: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. @@ -144,7 +144,7 @@ To allow TiDB Cloud to access the source data in your GCS bucket, you need to co > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. diff --git a/tidb-cloud/configure-maintenance-window.md b/tidb-cloud/configure-maintenance-window.md index 2916235fff08d..04b3dee0ce33c 100644 --- a/tidb-cloud/configure-maintenance-window.md +++ b/tidb-cloud/configure-maintenance-window.md @@ -55,15 +55,9 @@ If a maintenance window is planned, the default start time of the window is 03:0 You can modify the start time to your preferred time or defer maintenance tasks until the deadline as follows: -1. In the [TiDB Cloud console](https://tidbcloud.com/), navigate to the [Clusters](https://tidbcloud.com/console/clusters) page of your project. - - > **Note:** - > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. - -2. In the left navigation bar, click **Admin**. - -3. On the **Admin** page, click **Maintenance** in the left navigation pane. +1. Log in to the [TiDB Cloud console](https://tidbcloud.com). +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Maintenance** in the left navigation pane. - If any maintenance tasks are displayed, check the descriptions, scheduled start time, and deadline. The maintenance tasks will start at the designated time. diff --git a/tidb-cloud/configure-security-settings.md b/tidb-cloud/configure-security-settings.md index 39d384e32280f..c45b5705bbd4d 100644 --- a/tidb-cloud/configure-security-settings.md +++ b/tidb-cloud/configure-security-settings.md @@ -15,7 +15,7 @@ For TiDB Dedicated clusters, you can configure the root password and allowed IP > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. In the row of your target cluster, click **...** and select **Security Settings**. 3. In the **Security Settings** dialog, configure the root password and allowed IP addresses. diff --git a/tidb-cloud/connect-via-sql-shell.md b/tidb-cloud/connect-via-sql-shell.md index 4e042477c6a44..a6d3c26e1b6fe 100644 --- a/tidb-cloud/connect-via-sql-shell.md +++ b/tidb-cloud/connect-via-sql-shell.md @@ -9,7 +9,7 @@ In TiDB Cloud SQL Shell, you can try TiDB SQL, test out TiDB's compatibility wit > **Note:** > -> You cannot connect to [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) using SQL Shell. To connect to your TiDB Serverless cluster, see [Connect to TiDB Serverless clusters](/tidb-cloud/connect-to-tidb-cluster-serverless.md). +> You cannot connect to [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless) using SQL Shell. To connect to your TiDB Serverless cluster, see [Connect to TiDB Serverless clusters](/tidb-cloud/connect-to-tidb-cluster-serverless.md). To connect to your TiDB cluster using SQL shell, perform the following steps: @@ -17,7 +17,7 @@ To connect to your TiDB cluster using SQL shell, perform the following steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its cluster overview page, and then click **Connect** in the upper-right corner. A connection dialog is displayed. diff --git a/tidb-cloud/connect-via-standard-connection.md b/tidb-cloud/connect-via-standard-connection.md index 0514719d120f0..922b94825cffc 100644 --- a/tidb-cloud/connect-via-standard-connection.md +++ b/tidb-cloud/connect-via-standard-connection.md @@ -19,7 +19,7 @@ To connect to a TiDB Dedicated cluster via standard connection, take the followi > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page. diff --git a/tidb-cloud/create-tidb-cluster.md b/tidb-cloud/create-tidb-cluster.md index f2a5837bda93c..63f27edab0cc3 100644 --- a/tidb-cloud/create-tidb-cluster.md +++ b/tidb-cloud/create-tidb-cluster.md @@ -25,7 +25,7 @@ Once you log in to the [TiDB Cloud console](https://tidbcloud.com/), you have a If you are an organization owner, you can rename the default project or create a new project for the cluster according to your need as follows: -1. Log in to the [TiDB Cloud console](https://tidbcloud.com/), and then click **Organization** in the upper-right corner. +1. Log in to the [TiDB Cloud console](https://tidbcloud.com/), and then click in the lower-left corner. 2. Click **Organization Settings**. @@ -46,7 +46,7 @@ To create a TiDB Dedicated cluster, take the following steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click **Create Cluster**. diff --git a/tidb-cloud/data-service-get-started.md b/tidb-cloud/data-service-get-started.md index 6fda67d6222ea..b0964eb228e22 100644 --- a/tidb-cloud/data-service-get-started.md +++ b/tidb-cloud/data-service-get-started.md @@ -17,7 +17,7 @@ This document introduces how to quickly get started with TiDB Cloud Data Service ## Before you begin -Before creating a Data App, make sure that you have created a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster. If you do not have one, follow the steps in [Create a TiDB Serverless cluster](/tidb-cloud/create-tidb-cluster-serverless.md) to create one. +Before creating a Data App, make sure that you have created a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster. If you do not have one, follow the steps in [Create a TiDB Serverless cluster](/tidb-cloud/create-tidb-cluster-serverless.md) to create one. ## Step 1. Create a Data App diff --git a/tidb-cloud/data-service-overview.md b/tidb-cloud/data-service-overview.md index ef11fbd76ad2b..fe016f860d168 100644 --- a/tidb-cloud/data-service-overview.md +++ b/tidb-cloud/data-service-overview.md @@ -9,7 +9,7 @@ TiDB Cloud provides a [Data Service (beta)](https://tidbcloud.com/console/data-s > **Note:** > -> Data Service is available for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. To use Data Service in TiDB Dedicated clusters, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md). +> Data Service is available for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. To use Data Service in TiDB Dedicated clusters, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md). An endpoint in Data Service is a web API that you can customize to execute SQL statements. You can specify parameters for your SQL statements, such as the value used in the `WHERE` clause. When a client calls an endpoint and provides values for the parameters in a request URL, the endpoint executes the corresponding SQL statement with the provided parameters and returns the results as part of the HTTP response. diff --git a/tidb-cloud/delete-tidb-cluster.md b/tidb-cloud/delete-tidb-cluster.md index a1d5fac6280d7..d8d042d9bbec0 100644 --- a/tidb-cloud/delete-tidb-cluster.md +++ b/tidb-cloud/delete-tidb-cluster.md @@ -23,7 +23,7 @@ You can delete a cluster at any time by performing the following steps: > **Note:** > - > [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) only support [in-place restoring from backups](/tidb-cloud/backup-and-restore-serverless.md#restore) and do not support restoring data after the deletion. If you want to delete a TiDB Serverless cluster and restore its data in the future, you can use [Dumpling](https://docs.pingcap.com/tidb/stable/dumpling-overview) to export your data as a backup. + > [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless) only support [in-place restoring from backups](/tidb-cloud/backup-and-restore-serverless.md#restore) and do not support restoring data after the deletion. If you want to delete a TiDB Serverless cluster and restore its data in the future, you can use [Dumpling](https://docs.pingcap.com/tidb/stable/dumpling-overview) to export your data as a backup. 5. Click **I understand the consequences. Delete this cluster**. diff --git a/tidb-cloud/explore-data-with-chat2query.md b/tidb-cloud/explore-data-with-chat2query.md index 9a17201499749..cf35fd0687a23 100644 --- a/tidb-cloud/explore-data-with-chat2query.md +++ b/tidb-cloud/explore-data-with-chat2query.md @@ -13,7 +13,7 @@ In Chat2Query, you can either simply type `--` followed by your instructions to > > Chat2Query is supported for TiDB clusters that are v6.5.0 or later and are hosted on AWS. > -> - For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters, Chat2Query is available by default. +> - For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters, Chat2Query is available by default. > - For [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters, Chat2Query is only available upon request. To use Chat2Query on TiDB Dedicated clusters, contact [TiDB Cloud support](/tidb-cloud/tidb-cloud-support.md). ## Use cases @@ -27,7 +27,7 @@ The recommended use cases of Chat2Query are as follows: ## Limitation - SQL queries generated by the AI are not 100% accurate and might still need your further tweak. -- The [Chat2Query API](/tidb-cloud/use-chat2query-api.md) is available for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. To use the Chat2Query API on [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters, contact [TiDB Cloud support](/tidb-cloud/tidb-cloud-support.md). +- The [Chat2Query API](/tidb-cloud/use-chat2query-api.md) is available for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. To use the Chat2Query API on [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters, contact [TiDB Cloud support](/tidb-cloud/tidb-cloud-support.md). ## Access Chat2Query @@ -35,7 +35,7 @@ The recommended use cases of Chat2Query are as follows: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click your cluster name, and then click **Chat2Query** in the left navigation pane. @@ -59,7 +59,7 @@ When you access Chat2Query for the first time, you will be prompted with a dialo After the first-time access, you can still change the AI setting as follows: - To enable AI, click **Enable AI power for data exploration** in the upper-right corner of Chat2Query. -- To disable AI, click **Account** in the upper-right corner of the [TiDB Cloud console](https://tidbcloud.com/), click **Account Settings**, click the **Privacy** tab, and then disable the **AI-powered Data Exploration** option. +- To disable AI, click in the lower-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click **Account Settings**, click the **Privacy** tab, and then disable the **AI-powered Data Exploration** option. ## Write and run SQL queries diff --git a/tidb-cloud/get-started-with-cli.md b/tidb-cloud/get-started-with-cli.md index 47f31093bc395..dad82fe45d193 100644 --- a/tidb-cloud/get-started-with-cli.md +++ b/tidb-cloud/get-started-with-cli.md @@ -55,7 +55,7 @@ Install the MySQL command-line client if you do not have it. You can install it ```shell sudo yum install mysql ``` - + - macOS: ```shell @@ -125,7 +125,7 @@ tiup update cloud ## Quick start -[TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) (Beta) is the best way to get started with TiDB Cloud. In this section, you will learn how to create a TiDB Serverless cluster with TiDB Cloud CLI. +[TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) is the best way to get started with TiDB Cloud. In this section, you will learn how to create a TiDB Serverless cluster with TiDB Cloud CLI. ### Create a user profile diff --git a/tidb-cloud/import-csv-files.md b/tidb-cloud/import-csv-files.md index 58c3c7d02fa47..0fc06cf2ff05a 100644 --- a/tidb-cloud/import-csv-files.md +++ b/tidb-cloud/import-csv-files.md @@ -93,7 +93,7 @@ To import the CSV files to TiDB Cloud, take the following steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. diff --git a/tidb-cloud/import-parquet-files.md b/tidb-cloud/import-parquet-files.md index 7c0c30172bcb4..b62ace91270e4 100644 --- a/tidb-cloud/import-parquet-files.md +++ b/tidb-cloud/import-parquet-files.md @@ -100,7 +100,7 @@ To import the Parquet files to TiDB Cloud, take the following steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. diff --git a/tidb-cloud/import-sample-data.md b/tidb-cloud/import-sample-data.md index 7e360504cbf13..1a00d999a3290 100644 --- a/tidb-cloud/import-sample-data.md +++ b/tidb-cloud/import-sample-data.md @@ -13,7 +13,7 @@ This document describes how to import the sample data into TiDB Cloud via the UI > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. diff --git a/tidb-cloud/integrate-tidbcloud-with-airbyte.md b/tidb-cloud/integrate-tidbcloud-with-airbyte.md index 13860d51f29a5..c6ace16dfe33b 100644 --- a/tidb-cloud/integrate-tidbcloud-with-airbyte.md +++ b/tidb-cloud/integrate-tidbcloud-with-airbyte.md @@ -54,7 +54,7 @@ Conveniently, the steps are the same for setting TiDB as the source and the dest - Username: The username to access the database - Password: The password of the username - You can get the parameter values from the connection dialog of your cluster. To open the dialog, click the ☰ hover menu in the upper-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. + You can get the parameter values from the connection dialog of your cluster. To open the dialog, go to the [**Clusters**](https://tidbcloud.com/console/clusters) page of your project, click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. 3. Enable **SSL Connection**, and set TLS protocols to **TLSv1.2** or **TLSv1.3** in **JDBC URL Params**. diff --git a/tidb-cloud/integrate-tidbcloud-with-dbt.md b/tidb-cloud/integrate-tidbcloud-with-dbt.md index 8f17611e79ae3..ab90fa8111b71 100644 --- a/tidb-cloud/integrate-tidbcloud-with-dbt.md +++ b/tidb-cloud/integrate-tidbcloud-with-dbt.md @@ -90,7 +90,7 @@ To configure the project, take the following steps: password: "your_password" # The password to use for authenticating to the TiDB Cloud clusters ``` - You can get the values of `server`, `port`, and `username` from the connection dialog of your cluster. To open this dialog, click the ☰ hover menu in the upper-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. + You can get the values of `server`, `port`, and `username` from the connection dialog of your cluster. To open this dialog, go to the [**Clusters**](https://tidbcloud.com/console/clusters) page of your project, click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. 2. Complete the project configuration. diff --git a/tidb-cloud/integrate-tidbcloud-with-n8n.md b/tidb-cloud/integrate-tidbcloud-with-n8n.md index ae544d15be694..e815286686217 100644 --- a/tidb-cloud/integrate-tidbcloud-with-n8n.md +++ b/tidb-cloud/integrate-tidbcloud-with-n8n.md @@ -12,7 +12,7 @@ This document introduces how to build an auto-workflow: create a TiDB Serverless ## Prerequisites: Get TiDB Cloud API key 1. Access your TiDB Cloud dashboard. -2. Click **Organization** > **Organization Settings** in the upper-right corner. +2. Click , and then click **Organization Settings** in the lower-left corner. 3. Click the **API Keys** tab. 4. Click the **Create API Key** button to create a new API key. 5. Save the created API key for later use in n8n. diff --git a/tidb-cloud/integrate-tidbcloud-with-netlify.md b/tidb-cloud/integrate-tidbcloud-with-netlify.md index 60314a8090082..60e252ccef185 100644 --- a/tidb-cloud/integrate-tidbcloud-with-netlify.md +++ b/tidb-cloud/integrate-tidbcloud-with-netlify.md @@ -99,7 +99,7 @@ For a TiDB Dedicated cluster, you can get the connection string only from the Ti
-1. In the [TiDB Cloud console](https://tidbcloud.com/), click the ☰ hover menu in the upper-left corner, click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. In the displayed dialog, you can get the following connection parameters from the connection string. +1. In the [TiDB Cloud console](https://tidbcloud.com/), go to the [**Clusters**](https://tidbcloud.com/console/clusters) page of your project, click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. In the displayed dialog, you can get the following connection parameters from the connection string. - `${host}` - `${port}` diff --git a/tidb-cloud/integrate-tidbcloud-with-vercel.md b/tidb-cloud/integrate-tidbcloud-with-vercel.md index 3cf7f279db90f..1e25711d37296 100644 --- a/tidb-cloud/integrate-tidbcloud-with-vercel.md +++ b/tidb-cloud/integrate-tidbcloud-with-vercel.md @@ -152,7 +152,7 @@ The detailed steps are as follows: 1. Get the connection information of your TiDB cluster. - You can get the connection information from the connection dialog of your cluster. To open the dialog, click the ☰ hover menu in the upper-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. + You can get the connection information from the connection dialog of your cluster. To open the dialog, go to the [**Clusters**](https://tidbcloud.com/console/clusters) page of your project, click the name of your target cluster to go to its overview page, and then click **Connect** in the upper-right corner. > **Note:** > diff --git a/tidb-cloud/manage-serverless-spend-limit.md b/tidb-cloud/manage-serverless-spend-limit.md index ea385e31ac05a..1b31e9fa05e3c 100644 --- a/tidb-cloud/manage-serverless-spend-limit.md +++ b/tidb-cloud/manage-serverless-spend-limit.md @@ -17,7 +17,7 @@ For each organization in TiDB Cloud, you can create a maximum of five TiDB Serve For the first five TiDB Serverless clusters in your organization, TiDB Cloud provides a free usage quota for each of them as follows: -- Row storage: 5 GiB +- Row-based storage: 5 GiB - [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit): 50 million RUs per month Once the free quota of a cluster is reached, the read and write operations on this cluster will be throttled until you [increase the quota](#update-spend-limit) or the usage is reset upon the start of a new month. For example, when the storage of a cluster exceeds 5 GiB, the maximum size limit of a single transaction is reduced from 10 MiB to 1 MiB. @@ -30,12 +30,15 @@ If you want to create a TiDB Serverless cluster with an additional quota, you ca For an existing TiDB Serverless cluster, you can increase the usage quota by updating the spend limit as follows: -1. In the TiDB Cloud console, click the ☰ hover menu in the upper-left corner, and then click the name of your target cluster to go to its overview page. +1. On the [**Clusters**](https://tidbcloud.com/console/clusters) page of your project, click the name of your target cluster to go to its overview page. > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project in the ☰ hover menu. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. In the **Usage This Month** area, click **Get more usage quota**. + + If you have previously updated the spend limit for a cluster and want to increase it further, click **Edit**. + 3. Edit the monthly spend limit as needed. If you have not added a payment method, you will need to add a credit card after editing the limit. -4. Click **Update spend limit**. +4. Click **Update Spend Limit**. diff --git a/tidb-cloud/manage-user-access.md b/tidb-cloud/manage-user-access.md index b71a667ffc243..654858f680fdb 100644 --- a/tidb-cloud/manage-user-access.md +++ b/tidb-cloud/manage-user-access.md @@ -29,7 +29,7 @@ Under this structure: To check which organizations you belong to, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. You can view your organization on the page that is displayed. ### Switch between organizations @@ -38,7 +38,7 @@ If you are a member of multiple organizations, you can switch your account betwe To switch between organizations, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Select **Switch Organization** in the drop-down menu, and click the organization you want to switch to. ### Set the time zone for your organization @@ -47,7 +47,7 @@ If you are the organization owner, you can modify the system display time accord To change the local timezone setting, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The organization settings page is displayed. @@ -63,7 +63,7 @@ If you are the owner of an organization, you can invite organization members. To invite a member to an organization, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The organization settings page is displayed. @@ -97,7 +97,7 @@ To remove a member from an organization, take the following steps: > > If a member is removed from an organization, the member is removed from the belonged projects either. -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The organization settings page is displayed. @@ -111,13 +111,13 @@ To remove a member from an organization, take the following steps: To check which project you belong to, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The **Projects** tab is displayed by default. > **Tip:** > -> If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. +> If you have multiple projects, you can click in the lower-left corner and switch to another project. ### Create a project @@ -127,7 +127,7 @@ To check which project you belong to, take the following steps: To create a new project, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The **Projects** tab is displayed by default. @@ -141,7 +141,7 @@ To create a new project, take the following steps: To rename a project, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The **Projects** tab is displayed by default. @@ -157,7 +157,7 @@ If you are the owner of an organization, you can invite project members. To invite a member to a project, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The organization settings page is displayed. @@ -187,7 +187,7 @@ If you are the owner of an organization, you can remove project members. To remove a member from a project, take the following steps: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The organization settings page is displayed. @@ -199,7 +199,7 @@ To remove a member from a project, take the following steps: If you are the owner of an organization, you can take the following steps to configure roles for your organization members: -1. Click **Organization** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Organization Settings**. The organization settings page is displayed. @@ -233,7 +233,7 @@ There are four roles in an organization. The permissions of each role are as fol In TiDB Cloud, you can easily manage your profile, including your first name, last name, and phone number. -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Account Settings**. The **Profile** tab is displayed by default. diff --git a/tidb-cloud/migrate-data-into-tidb.md b/tidb-cloud/migrate-data-into-tidb.md index af99af7f03fc5..871e7d84b67c5 100644 --- a/tidb-cloud/migrate-data-into-tidb.md +++ b/tidb-cloud/migrate-data-into-tidb.md @@ -100,7 +100,7 @@ Depending on the location and size of your source data, the importing methods ar > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 3. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. 4. On the **Import** page, click **Import Data** in the upper-right corner, select **From S3**, and then fill in the importing related information. diff --git a/tidb-cloud/migrate-from-amazon-s3-or-gcs.md b/tidb-cloud/migrate-from-amazon-s3-or-gcs.md index b0dbfd069f4db..bee8a72984f39 100644 --- a/tidb-cloud/migrate-from-amazon-s3-or-gcs.md +++ b/tidb-cloud/migrate-from-amazon-s3-or-gcs.md @@ -67,7 +67,7 @@ For detailed steps, see [Configure Amazon S3 access](/tidb-cloud/config-s3-and-g > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. @@ -142,7 +142,7 @@ For detailed steps, see [Configure GCS access](/tidb-cloud/config-s3-and-gcs-acc > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 3. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. 4. On the **Import** page, click **Import Data** in the upper-right corner, and then fill in the importing related information. diff --git a/tidb-cloud/migrate-from-aurora-bulk-import.md b/tidb-cloud/migrate-from-aurora-bulk-import.md index 606ac8f946da6..e70abff0d1bd1 100644 --- a/tidb-cloud/migrate-from-aurora-bulk-import.md +++ b/tidb-cloud/migrate-from-aurora-bulk-import.md @@ -17,7 +17,7 @@ To import data, perform the following steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. diff --git a/tidb-cloud/migrate-from-mysql-using-data-migration.md b/tidb-cloud/migrate-from-mysql-using-data-migration.md index e9423824153bb..a42120ad0230c 100644 --- a/tidb-cloud/migrate-from-mysql-using-data-migration.md +++ b/tidb-cloud/migrate-from-mysql-using-data-migration.md @@ -155,7 +155,7 @@ To perform incremental data migration, make sure you have enabled binary logs of > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Data Migration** in the left navigation pane. diff --git a/tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md b/tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md index 4b2f86c2a6ad3..f508ad2104022 100644 --- a/tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md +++ b/tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md @@ -108,7 +108,7 @@ To enable the GTID mode for a self-hosted MySQL instance, follow these steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Data Migration** in the left navigation pane. diff --git a/tidb-cloud/migrate-sql-shards.md b/tidb-cloud/migrate-sql-shards.md index 87582fd2ed927..5550e0cd70b90 100644 --- a/tidb-cloud/migrate-sql-shards.md +++ b/tidb-cloud/migrate-sql-shards.md @@ -181,7 +181,7 @@ After configuring the Amazon S3 access, you can perform the data import task in > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. diff --git a/tidb-cloud/monitor-built-in-alerting.md b/tidb-cloud/monitor-built-in-alerting.md index 11ac7c5053051..8be4892790483 100644 --- a/tidb-cloud/monitor-built-in-alerting.md +++ b/tidb-cloud/monitor-built-in-alerting.md @@ -21,7 +21,7 @@ In TiDB Cloud, you can view both active and closed alerts on the Alerts page. > **Tip:** > - > If you have multiple projects, you can switch to the target project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of the target cluster. The cluster overview page is displayed. 3. Click **Alerts** in the left navigation pane. @@ -54,12 +54,9 @@ To get alert notification emails of clusters in your project, take the following Alternatively, you can also add the subscription from the **Alert Subscription** page as follows: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Alert Subscription**. - - If you only have one project, click **Admin** > **Alert Subscription**. - -3. Click **Add Subscriber**, enter your email address in the displayed dialog, and then click **Add**. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Alert Subscription** in the left navigation pane. +4. Click **Add Subscriber**, enter your email address in the displayed dialog, and then click **Add**. If an alert condition remains unchanged, the alert sends email notifications every 3 hours. @@ -68,14 +65,10 @@ If an alert condition remains unchanged, the alert sends email notifications eve If you no longer want to receive alert notification emails of clusters in your project, take the following steps: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Alert Subscription**. - - If you only have one project, click **Admin** > **Alert Subscription**. - -3. Locate your email address and click **Unsubscribe**. - -4. Click **Delete** to confirm the unsubscription. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Alert Subscription** in the left navigation pane. +4. Locate your email address and click **Unsubscribe**. +5. Click **Delete** to confirm the unsubscription. ## TiDB Cloud built-in alert conditions diff --git a/tidb-cloud/monitor-datadog-integration.md b/tidb-cloud/monitor-datadog-integration.md index 7ad6916e2638c..34a5da3e23298 100644 --- a/tidb-cloud/monitor-datadog-integration.md +++ b/tidb-cloud/monitor-datadog-integration.md @@ -1,11 +1,11 @@ --- -title: Integrate TiDB Cloud with Datadog +title: Integrate TiDB Cloud with Datadog (Beta) summary: Learn how to monitor your TiDB cluster with the Datadog integration. --- -# Integrate TiDB Cloud with Datadog +# Integrate TiDB Cloud with Datadog (Beta) -You can configure TiDB Cloud to send metric data about your TiDB clusters to [Datadog](https://www.datadoghq.com/). After that, you can view these metrics in your Datadog dashboards directly. +TiDB Cloud supports Datadog integration (beta). You can configure TiDB Cloud to send metric data about your TiDB clusters to [Datadog](https://www.datadoghq.com/). After that, you can view these metrics in your Datadog dashboards directly. ## Prerequisites @@ -17,7 +17,7 @@ You can configure TiDB Cloud to send metric data about your TiDB clusters to [Da ## Limitation -- You cannot use the Datadog integration in [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- You cannot use the Datadog integration in [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. - Datadog integrations are not available when the cluster status is **CREATING**, **RESTORING**, **PAUSED**, or **RESUMING**. @@ -26,12 +26,8 @@ You can configure TiDB Cloud to send metric data about your TiDB clusters to [Da ### Step 1. Integrate with your Datadog API Key 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Integrations**. - - If you only have one project, click **Admin** > **Integrations**. - -3. Click **Integration to Datadog**. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Integrations** in the left navigation pane, and then click **Integration to Datadog (BETA)**. 4. Enter your API key of Datadog and choose the site of Datadog. 5. Click **Test Integration**. diff --git a/tidb-cloud/monitor-new-relic-integration.md b/tidb-cloud/monitor-new-relic-integration.md index c0e58f0751979..7e9730f993860 100644 --- a/tidb-cloud/monitor-new-relic-integration.md +++ b/tidb-cloud/monitor-new-relic-integration.md @@ -1,11 +1,11 @@ --- -title: Integrate TiDB Cloud with New Relic +title: Integrate TiDB Cloud with New Relic (Beta) summary: Learn how to monitor your TiDB cluster with the New Relic integration. --- -# Integrate TiDB Cloud with New Relic +# Integrate TiDB Cloud with New Relic (Beta) -You can configure TiDB Cloud to send metric data of your TiDB clusters to [New Relic](https://newrelic.com/). After that, you can directly view these metrics in your New Relic dashboards. +TiDB Cloud supports New Relic integration (beta). You can configure TiDB Cloud to send metric data of your TiDB clusters to [New Relic](https://newrelic.com/). After that, you can directly view these metrics in your New Relic dashboards. ## Prerequisites @@ -17,19 +17,15 @@ You can configure TiDB Cloud to send metric data of your TiDB clusters to [New R ## Limitation -You cannot use the New Relic integration in [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +You cannot use the New Relic integration in [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless). ## Steps ### Step 1. Integrate with your New Relic API Key 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Integrations**. - - If you only have one project, click **Admin** > **Integrations**. - -3. Click **Integration to New Relic**. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Integrations** in the left navigation pane, and then click **Integration to New Relic (BETA)**. 4. Enter your API key of New Relic and choose the site of New Relic. 5. Click **Test Integration**. diff --git a/tidb-cloud/monitor-prometheus-and-grafana-integration.md b/tidb-cloud/monitor-prometheus-and-grafana-integration.md index 25aafa30a9489..fcc78f6f35e0b 100644 --- a/tidb-cloud/monitor-prometheus-and-grafana-integration.md +++ b/tidb-cloud/monitor-prometheus-and-grafana-integration.md @@ -1,11 +1,11 @@ --- -title: Integrate TiDB Cloud with Prometheus and Grafana +title: Integrate TiDB Cloud with Prometheus and Grafana (Beta) summary: Learn how to monitor your TiDB cluster with the Prometheus and Grafana integration. --- -# Integrate TiDB Cloud with Prometheus and Grafana +# Integrate TiDB Cloud with Prometheus and Grafana (Beta) -TiDB Cloud provides a [Prometheus](https://prometheus.io/) API endpoint. If you have a Prometheus service, you can monitor key metrics of TiDB Cloud from the endpoint easily. +TiDB Cloud provides a [Prometheus](https://prometheus.io/) API endpoint (beta). If you have a Prometheus service, you can monitor key metrics of TiDB Cloud from the endpoint easily. This document describes how to configure your Prometheus service to read key metrics from the TiDB Cloud endpoint and how to view the metrics using [Grafana](https://grafana.com/). @@ -17,7 +17,7 @@ This document describes how to configure your Prometheus service to read key met ## Limitation -- You cannot use the Prometheus and Grafana integration in [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- You cannot use the Prometheus and Grafana integration in [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. - Prometheus and Grafana integrations are not available when the cluster status is **CREATING**, **RESTORING**, **PAUSED**, or **RESUMING**. @@ -30,12 +30,8 @@ Before configuring your Prometheus service to read metrics of TiDB Cloud, you ne To get the scrape_config file for Prometheus, do the following: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Integrations**. - - If you only have one project, click **Admin** > **Integrations**. - -3. Click **Integration to Prometheus**. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Integrations** in the left navigation pane, and then click **Integration to Prometheus (BETA)**. 4. Click **Add File** to generate and show the scrape_config file for the current project. 5. Make a copy of the scrape_config file content for later use. diff --git a/tidb-cloud/monitor-tidb-cluster.md b/tidb-cloud/monitor-tidb-cluster.md index 2b6076806cec0..8c148b969a106 100644 --- a/tidb-cloud/monitor-tidb-cluster.md +++ b/tidb-cloud/monitor-tidb-cluster.md @@ -78,7 +78,7 @@ The cluster monitoring page provides a full set of standard metrics of a cluster > **Note:** > -> Currently, the cluster monitoring page is unavailable for [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +> Currently, the cluster monitoring page is unavailable for [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless). To view metrics on the cluster monitoring page, take the following steps: diff --git a/tidb-cloud/pause-or-resume-tidb-cluster.md b/tidb-cloud/pause-or-resume-tidb-cluster.md index c5cee33aba3b7..b0317c2051ba3 100644 --- a/tidb-cloud/pause-or-resume-tidb-cluster.md +++ b/tidb-cloud/pause-or-resume-tidb-cluster.md @@ -13,7 +13,7 @@ Comparing with backup and restore, pausing and resuming a cluster takes less tim > **Note:** > -> You cannot pause a [TiDB Serverless cluster](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +> You cannot pause a [TiDB Serverless cluster](/tidb-cloud/select-cluster-tier.md#tidb-serverless). ## Limitations diff --git a/tidb-cloud/release-notes-2021.md b/tidb-cloud/release-notes-2021.md index 3a378cfdc370d..f752501b48ef8 100644 --- a/tidb-cloud/release-notes-2021.md +++ b/tidb-cloud/release-notes-2021.md @@ -40,7 +40,7 @@ Bug fixes: ## November 8, 2021 -* Launch [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta), which offers you a one-year free trial of TiDB Cloud +* Launch [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless), which offers you a one-year free trial of TiDB Cloud Each Developer Tier cluster is a full-featured TiDB cluster and comes with the following: diff --git a/tidb-cloud/release-notes-2022.md b/tidb-cloud/release-notes-2022.md index f6155e7e21132..44e72a9a48d91 100644 --- a/tidb-cloud/release-notes-2022.md +++ b/tidb-cloud/release-notes-2022.md @@ -11,13 +11,13 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -- Currently, after upgrading the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters from [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0) to [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0), the cold start becomes slower in certain circumstances. So we roll back the default TiDB version of all Serverless Tier clusters from v6.4.0 to v6.3.0, then fix the problem as soon as possible, and upgrade it later again. +- Currently, after upgrading the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters from [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0) to [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0), the cold start becomes slower in certain circumstances. So we roll back the default TiDB version of all Serverless Tier clusters from v6.4.0 to v6.3.0, then fix the problem as soon as possible, and upgrade it later again. ## December 27, 2022 **General changes** -- Upgrade the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters from [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0) to [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0). +- Upgrade the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters from [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0) to [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0). - The point-in-time recovery (PITR) for Dedicated Tier clusters is now in General Availability (GA). @@ -169,7 +169,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -* Developer Tier is upgraded to [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). Serverless Tier, a fully-managed, auto-scaling deployment of TiDB, is now available. It is still in beta and free to use. +* Developer Tier is upgraded to [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless). Serverless Tier, a fully-managed, auto-scaling deployment of TiDB, is now available. It is still in beta and free to use. * A Serverless Tier cluster still contains fully functional HTAP ability as Dedicated Tier clusters. * Serverless Tier offers you faster cluster creation time and instantaneous cold start time. Compared with Developer Tier, the creation time reduces from minutes to seconds. @@ -247,7 +247,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -* Upgrade the default TiDB version of new [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters from [v6.2.0](https://docs.pingcap.com/tidb/v6.2/release-6.2.0) to [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0). +* Upgrade the default TiDB version of new [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters from [v6.2.0](https://docs.pingcap.com/tidb/v6.2/release-6.2.0) to [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0). **Console changes** @@ -310,7 +310,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c In the new design, the entrances of upgrade to Dedicated Tier, cluster connection, and data import are highlighted. -* Introduce Playground for [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +* Introduce Playground for [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. Playground contains a pre-loaded dataset of GitHub events, which allows you to get started with TiDB Cloud by running queries instantly, without importing your data or connecting to a client. @@ -374,7 +374,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -* Upgrade the default TiDB version of new [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters from [v6.1.0](https://docs.pingcap.com/tidb/stable/release-6.1.0) to [v6.2.0](https://docs.pingcap.com/tidb/v6.2/release-6.2.0). +* Upgrade the default TiDB version of new [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters from [v6.1.0](https://docs.pingcap.com/tidb/stable/release-6.1.0) to [v6.2.0](https://docs.pingcap.com/tidb/v6.2/release-6.2.0). **API changes** @@ -441,19 +441,19 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c ## July 26, 2022 -* Support automatic hibernation and resuming for new [Developer Tier clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +* Support automatic hibernation and resuming for new [Developer Tier clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless). A Developer Tier cluster will not be deleted after 7 days of inactivity so you can still use it at any time until the one-year free trial ends. After 24 hours of inactivity, the Developer Tier cluster will hibernate automatically. To resume the cluster, either send a new connection to the cluster or click the **Resume** button in the TiDB Cloud console. The cluster will be resumed within 50 seconds and back to service automatically. -* Add a user name prefix limitation for new [Developer Tier clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +* Add a user name prefix limitation for new [Developer Tier clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless). Whenever you use or set a database user name, you must include the prefix for your cluster in the user name. For more information, see [User name prefix](/tidb-cloud/select-cluster-tier.md#user-name-prefix). -* Disable the backup and restore feature for [Developer Tier clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +* Disable the backup and restore feature for [Developer Tier clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless). The backup and restore feature (including both automatic backup and manual backup) is disabled for Developer Tier clusters. You can still use [Dumpling](https://docs.pingcap.com/tidb/stable/dumpling-overview) to export your data as a backup. -* Increase the storage size of a [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster from 500 MiB to 1 GiB. +* Increase the storage size of a [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster from 500 MiB to 1 GiB. * Add breadcrumbs to the TiDB Cloud console to improve the navigation experience. * Support configuring multiple filter rules when you import data into TiDB Cloud. * Remove the **Traffic Filters** page from **Project Settings**, and remove the **Add Rules from Default Set** button from the **Connect to TiDB** dialog. @@ -526,7 +526,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c ## May 19, 2022 -* Add the support of the AWS region `Frankfurt` for [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster creation. +* Add the support of the AWS region `Frankfurt` for [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster creation. ## May 18, 2022 @@ -550,7 +550,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c TiDB Cloud is now in General Availability. You can [sign up](https://tidbcloud.com/signup) and select one of the following options: -* Get started with [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) for free. +* Get started with [Developer Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) for free. * Apply for [a 14-day PoC trial for free](https://en.pingcap.com/apply-for-poc/). * Get full access with [Dedicated Tier](/tidb-cloud/select-cluster-tier.md#tidb-dedicated). diff --git a/tidb-cloud/scale-tidb-cluster.md b/tidb-cloud/scale-tidb-cluster.md index 951547671ff05..c04f7df60524a 100644 --- a/tidb-cloud/scale-tidb-cluster.md +++ b/tidb-cloud/scale-tidb-cluster.md @@ -7,7 +7,7 @@ summary: Learn how to scale your TiDB Cloud cluster. > **Note:** > -> - You cannot scale a [TiDB Serverless cluster](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta). +> - You cannot scale a [TiDB Serverless cluster](/tidb-cloud/select-cluster-tier.md#tidb-serverless). > - When a cluster is in the **MODIFYING** status, you cannot perform any new scaling operations on it. You can scale a TiDB cluster in the following dimensions: diff --git a/tidb-cloud/select-cluster-tier.md b/tidb-cloud/select-cluster-tier.md index 709e5a2335824..c55d67a527577 100644 --- a/tidb-cloud/select-cluster-tier.md +++ b/tidb-cloud/select-cluster-tier.md @@ -10,12 +10,13 @@ The cluster tier determines the throughput and performance of your cluster. TiDB Cloud provides the following two options of cluster tiers. Before creating a cluster, you need to consider which option suits your need better. -- [TiDB Serverless](#tidb-serverless-beta) +- [TiDB Serverless](#tidb-serverless) - [TiDB Dedicated](#tidb-dedicated) -## TiDB Serverless (Beta) +## TiDB Serverless -TiDB Serverless (previously called Developer Tier) is a fully managed service of TiDB. It's still in beta and should not be used in production. However, you can use TiDB Serverless clusters for non-production workloads such as prototype applications, hackathons, academic courses, or to provide a temporary data service for your datasets. + +TiDB Serverless is a fully managed, multi-tenant TiDB offering. It delivers an instant, autoscaling MySQL-compatible database and offers a generous free tier and consumption based billing once free limits are exceeded. ### Usage quota @@ -23,7 +24,7 @@ For each organization in TiDB Cloud, you can create a maximum of five TiDB Serve For the first five TiDB Serverless clusters in your organization, TiDB Cloud provides a free usage quota for each of them as follows: -- Row storage: 5 GiB +- Row-based storage: 5 GiB - [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit): 50 million RUs per month A Request Unit (RU) is a unit of measure used to represent the amount of resources consumed by a single request to the database. The amount of RUs consumed by a request depends on various factors, such as the operation type or the amount of data being retrieved or modified. @@ -64,8 +65,7 @@ To get the prefix for your cluster, take the following steps: ### TiDB Serverless special terms and conditions -- TiDB Serverless is currently in beta and does not have uptime SLA guarantee during beta phase. If you use TiDB Serverless beta to store a commercial or production dataset, any potential risk associated with the use should be taken on your own, and PingCAP shall not be liable for any damage. -- Some of TiDB Cloud features are partially supported or not supported on TiDB Serverless. See [TiDB Serverless Limitations](/tidb-cloud/serverless-limitations.md) for details. +Some of TiDB Cloud features are partially supported or not supported on TiDB Serverless. See [TiDB Serverless Limitations](/tidb-cloud/serverless-limitations.md) for details. ## TiDB Dedicated diff --git a/tidb-cloud/serverless-limitations.md b/tidb-cloud/serverless-limitations.md index 5da65bcb9eca2..1a0d3d8bde559 100644 --- a/tidb-cloud/serverless-limitations.md +++ b/tidb-cloud/serverless-limitations.md @@ -17,7 +17,7 @@ We are constantly filling in the feature gaps between TiDB Serverless and TiDB D ### SQL - [Time to live (TTL)](/time-to-live.md) is not available for TiDB Serverless clusters currently. -- The [`FLASHBACK CLUSTER TO TIMESTAMP`](/sql-statements/sql-statement-flashback-to-timestamp.md) syntax is not applicable to [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- The [`FLASHBACK CLUSTER TO TIMESTAMP`](/sql-statements/sql-statement-flashback-to-timestamp.md) syntax is not applicable to [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. - The [`SLEEP()` function](/functions-and-operators/miscellaneous-functions.md) only supports a maximum sleep time of 300 seconds. ### System tables @@ -58,7 +58,7 @@ For each organization in TiDB Cloud, you can create a maximum of five TiDB Serve For the first five TiDB Serverless clusters in your organization, TiDB Cloud provides a free usage quota for each of them as follows: -- Row storage: 5 GiB +- Row-based storage: 5 GiB - [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit): 50 million RUs per month The Request Unit (RU) is a unit of measurement used to track the resource consumption of a query or transaction. It is a metric that allows you to estimate the computational resources required to process a specific request in the database. The request unit is also the billing unit for TiDB Cloud Serverless service. diff --git a/tidb-cloud/set-up-private-endpoint-connections.md b/tidb-cloud/set-up-private-endpoint-connections.md index 81f025f18e22c..e6ed1a5daded0 100644 --- a/tidb-cloud/set-up-private-endpoint-connections.md +++ b/tidb-cloud/set-up-private-endpoint-connections.md @@ -51,12 +51,8 @@ If you have multiple clusters, you need to repeat these steps for each cluster t ### Prerequisites 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Network Access**. - - If you only have one project, click **Admin** > **Network Access**. - -3. Click the **Private Endpoint** tab. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Network Access** in the left navigation pane, and click the **Private Endpoint** tab. 4. Click **Add** in the upper-right corner. ### Step 1. Choose a TiDB cluster diff --git a/tidb-cloud/set-up-vpc-peering-connections.md b/tidb-cloud/set-up-vpc-peering-connections.md index de2cd0718458b..ef2367c4ca267 100644 --- a/tidb-cloud/set-up-vpc-peering-connections.md +++ b/tidb-cloud/set-up-vpc-peering-connections.md @@ -7,7 +7,7 @@ summary: Learn how to connect to TiDB Dedicated via VPC peering. > **Note:** > -> VPC peering connection is only available for TiDB Dedicated clusters. You cannot connect to [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) using VPC peering. +> VPC peering connection is only available for TiDB Dedicated clusters. You cannot connect to [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless) using VPC peering. To connect your application to TiDB Cloud via VPC peering, you need to set up [VPC peering](/tidb-cloud/tidb-cloud-glossary.md#vpc-peering) with TiDB Cloud. This document walks you through setting up VPC peering connections [on AWS](#set-up-vpc-peering-on-aws) and [on GCP](#set-up-vpc-peering-on-gcp) and connecting to TiDB Cloud via a VPC peering. @@ -28,13 +28,8 @@ Before adding VPC Peering requests to a region, you need to set a project CIDR f You can set the project CIDR when creating the first TiDB Dedicated of your project. If you want to set the project CIDR before creating the cluster, perform the following operations: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Network Access**. - - If you only have one project, click **Admin** > **Network Access**. - -3. Click the **Project CIDR** tab. - +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Network Access** in the left navigation pane, and then click the **Project CIDR** tab. 4. Click **Add a project CIDR for AWS** or **Add a project CIDR for Google Cloud** according to your cloud provider, specify one of the following network addresses in the **Project CIDR** field, and then click **Confirm**. > **Note:** @@ -63,12 +58,8 @@ This section describes how to set up VPC peering connections on AWS. For GCP, se ### Step 1. Add VPC peering requests 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Network Access**. - - If you only have one project, click **Admin** > **Network Access**. - -3. Click the **VPC Peering** tab. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Network Access** in the left navigation pane, and then click the **VPC Peering** tab. The **VPC Peering** configuration is displayed by default. @@ -213,12 +204,8 @@ Now you have successfully set up the VPC peering connection. Next, [connect to t ## Set up VPC peering on GCP 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Network Access**. - - If you only have one project, click **Admin** > **Network Access**. - -3. Click the **VPC Peering** tab. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Network Access** in the left navigation pane, and then click the **VPC Peering** tab. The **VPC Peering** configuration is displayed by default. diff --git a/tidb-cloud/size-your-cluster.md b/tidb-cloud/size-your-cluster.md index 9f98c18ea2d36..b046c31d3b7e0 100644 --- a/tidb-cloud/size-your-cluster.md +++ b/tidb-cloud/size-your-cluster.md @@ -9,7 +9,7 @@ This document describes how to determine the size of a TiDB Dedicated cluster. > **Note:** > -> You cannot change the size of a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster. +> You cannot change the size of a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster. ## Size TiDB diff --git a/tidb-cloud/third-party-monitoring-integrations.md b/tidb-cloud/third-party-monitoring-integrations.md index 0f74034e4600e..6671eaa55086a 100644 --- a/tidb-cloud/third-party-monitoring-integrations.md +++ b/tidb-cloud/third-party-monitoring-integrations.md @@ -1,11 +1,11 @@ --- -title: Third-Party Metrics Integrations +title: Third-Party Metrics Integrations（Beta） summary: Learn how to use third-party metrics integrations. --- -# Third-Party Metrics Integrations +# Third-Party Metrics Integrations（Beta） -You can integrate TiDB Cloud with third-party metrics services to receive TiDB Cloud alerts and view the performance metrics of your TiDB cluster using the metrics services. +You can integrate TiDB Cloud with third-party metrics services to receive TiDB Cloud alerts and view the performance metrics of your TiDB cluster using the metrics services. The third-party metrics integrations are currently in beta. ## Required access @@ -14,34 +14,32 @@ To edit third-party integration settings, you must have the `Owner` access to yo ## View or modify third-party integrations 1. Log in to the [TiDB Cloud console](https://tidbcloud.com). -2. In the left navigation pane of the [**Clusters**](https://tidbcloud.com/console/clusters) page, do one of the following: - - - If you have multiple projects, switch to the target project, and then click **Admin** > **Integrations**. - - If you only have one project, click **Admin** > **Integrations**. +2. Click in the lower-left corner, switch to the target project if you have multiple projects, and then click **Admin**. +3. On the **Admin** page of your project, click **Integrations** in the left navigation pane. The available third-party integrations are displayed. ## Limitation -- For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters, third-party metrics integrations are not supported. +- For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters, third-party metrics integrations are not supported. - Third-party metrics integrations are not available when the cluster status is **CREATING**, **RESTORING**, **PAUSED**, or **RESUMING**. ## Available integrations -### Datadog integration +### Datadog integration (beta) With the Datadog integration, you can configure TiDB Cloud to send metric data about your TiDB clusters to [Datadog](https://www.datadoghq.com/) and view these metrics in your Datadog dashboards. For the detailed integration steps and a list of metrics that Datadog tracks, refer to [Integrate TiDB Cloud with Datadog](/tidb-cloud/monitor-datadog-integration.md). -### Prometheus and Grafana integration +### Prometheus and Grafana integration (beta) With the Prometheus and Grafana integration, you can get a scrape_config file for Prometheus from TiDB Cloud and use the content from the file to configure Prometheus. You can view these metrics in your Grafana dashboards. For the detailed integration steps and a list of metrics that Prometheus tracks, see [Integrate TiDB Cloud with Prometheus and Grafana](/tidb-cloud/monitor-prometheus-and-grafana-integration.md). -### New Relic integration +### New Relic integration (beta) With the New Relic integration, you can configure TiDB Cloud to send metric data about your TiDB clusters to [New Relic](https://newrelic.com/) and view these metrics in your New Relic dashboards. diff --git a/tidb-cloud/ticloud-cluster-connect-info.md b/tidb-cloud/ticloud-cluster-connect-info.md index fdb43cf2fe992..0e2c4ec1e28e1 100644 --- a/tidb-cloud/ticloud-cluster-connect-info.md +++ b/tidb-cloud/ticloud-cluster-connect-info.md @@ -13,7 +13,7 @@ ticloud cluster connect-info [flags] > **Note:** > -> Currently, this command only supports getting the connection string of a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster. +> Currently, this command only supports getting the connection string of a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster. ## Examples diff --git a/tidb-cloud/ticloud-cluster-create.md b/tidb-cloud/ticloud-cluster-create.md index 06daf4bc849dd..f9dbd9ba85b10 100644 --- a/tidb-cloud/ticloud-cluster-create.md +++ b/tidb-cloud/ticloud-cluster-create.md @@ -13,7 +13,7 @@ ticloud cluster create [flags] > **Note:** > -> Currently, you can only create a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster using the preceding command. +> Currently, you can only create a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster using the preceding command. ## Examples diff --git a/tidb-cloud/ticloud-connect.md b/tidb-cloud/ticloud-connect.md index c99e9fa658a00..0b982647662f5 100644 --- a/tidb-cloud/ticloud-connect.md +++ b/tidb-cloud/ticloud-connect.md @@ -13,7 +13,7 @@ ticloud connect [flags] > **Note:** > -> - If you are prompted about whether to use the default user, you can choose `Y` to use the default root user or choose `n` to specify another user. For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters, the name of the default root user has a [prefix](/tidb-cloud/select-cluster-tier.md#user-name-prefix) such as `3pTAoNNegb47Uc8`. +> - If you are prompted about whether to use the default user, you can choose `Y` to use the default root user or choose `n` to specify another user. For [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters, the name of the default root user has a [prefix](/tidb-cloud/select-cluster-tier.md#user-name-prefix) such as `3pTAoNNegb47Uc8`. > - The connection forces the [ANSI SQL mode](https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html#sqlmode_ansi) for the session. To exit the session, enter `\q`. ## Examples diff --git a/tidb-cloud/ticloud-import-start-local.md b/tidb-cloud/ticloud-import-start-local.md index d1bcd7ff80d8f..c3576a4f901ae 100644 --- a/tidb-cloud/ticloud-import-start-local.md +++ b/tidb-cloud/ticloud-import-start-local.md @@ -5,7 +5,7 @@ summary: The reference of `ticloud import start local`. # ticloud import start local -Import a local file to a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster: +Import a local file to a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster: ```shell ticloud import start local [flags] diff --git a/tidb-cloud/ticloud-import-start-mysql.md b/tidb-cloud/ticloud-import-start-mysql.md index 1d92e3c420982..3c67cc007d95a 100644 --- a/tidb-cloud/ticloud-import-start-mysql.md +++ b/tidb-cloud/ticloud-import-start-mysql.md @@ -5,7 +5,7 @@ summary: The reference of `ticloud import start mysql`. # ticloud import start mysql -Import a table from a MySQL-compatible database to a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster: +Import a table from a MySQL-compatible database to a [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster: ```shell ticloud import start mysql [flags] diff --git a/tidb-cloud/tidb-cloud-billing.md b/tidb-cloud/tidb-cloud-billing.md index 4f8e241384ca2..c82ab3a065037 100644 --- a/tidb-cloud/tidb-cloud-billing.md +++ b/tidb-cloud/tidb-cloud-billing.md @@ -7,7 +7,7 @@ summary: Learn about TiDB Cloud billing. > **Note:** > -> [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) are free until May 31, 2023, with a 100% discount off. After that, usage beyond the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota) will be charged. +> [TiDB Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-serverless) are free until May 31, 2023, with a 100% discount off. After that, usage beyond the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota) will be charged. TiDB Cloud charges according to the resources that you consume. You can visit the following pages to get more information about the pricing. @@ -40,11 +40,11 @@ For each monthly invoice: To view the list of invoices, perform the following steps: -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. The invoices page is displayed. @@ -60,11 +60,11 @@ After setting the payment method, TiDB Cloud will generate the invoice and billi To view the billing details, perform the following steps: -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. 3. Click **Bills**. The billing details page is displayed. @@ -90,11 +90,11 @@ The detailed information of your credits is available on the **Credits** page, i To view this page, perform the following steps: -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. 3. Click **Credits**. The credit details page is displayed. @@ -119,11 +119,11 @@ The discount information includes all discounts that you have received, the stat To view this page, perform the following steps: -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. 3. Click **Discounts**. The discount details page is displayed. @@ -148,11 +148,11 @@ The fee is deducted from a bound credit card according to your cluster usage. To - Anytime in the billing console: - 1. Click **Account** in the upper-right corner of the TiDB Cloud console. + 1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. 3. Under the **Payment Method** tab, click **Add a New Card**. @@ -166,11 +166,11 @@ You can bind multiple credit cards, and set one of them as the default credit ca To set the default credit card, perform the following steps: -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. 3. Click the **Payment Method** tab. @@ -182,11 +182,11 @@ The billing profile information includes the business legal address and tax regi To edit the billing profile information, perform the following steps: -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. 3. Click the **Payment Method** tab. @@ -198,11 +198,11 @@ If you are the owner or billing administrator of your organization, you can mana If you have agreed with our sales on a contract and received an email to review and accept the contract online, you can do the following: -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. > **Note:** > - > If you are in multiple organizations, select **Switch Organization** and switch your account to the target organization. + > If you are in multiple organizations, switch to your target organization by clicking its name. 2. Click **Billing**. 3. Click **Contract**. The contract list is displayed. diff --git a/tidb-cloud/tidb-cloud-console-auditing.md b/tidb-cloud/tidb-cloud-console-auditing.md index bc2e7c15cb7ab..9f8b8f93c8b03 100644 --- a/tidb-cloud/tidb-cloud-console-auditing.md +++ b/tidb-cloud/tidb-cloud-console-auditing.md @@ -17,15 +17,15 @@ TiDB Cloud provides the console audit logging feature to help you track various The console audit logging feature is disabled by default. To enable it, take the following steps: -1. In the upper-right corner of the [TiDB Cloud console](https://tidbcloud.com/), click **Organization** > **Console Audit Logging**. -2. Click **Setting** in the upper-right corner, and then enable console audit logging. +1. In the lower-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click , and then click **Console Audit Logging**. +2. Click **Settings** in the upper-right corner, and then enable console audit logging. ## Disable console audit logging To disable console audit logging, take the following steps: -1. In the upper-right corner of the [TiDB Cloud console](https://tidbcloud.com/), click **Organization** > **Console Audit Logging**. -2. Click **Setting** in the upper-right corner, and then disable console audit logging. +1. In the lower-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click , and then click **Console Audit Logging**. +2. Click **Settings** in the upper-right corner, and then disable console audit logging. ## View console audit logs @@ -36,7 +36,7 @@ You can only view the console audit logs of your organization. > - If it is the first time your organization enables console audit logging, the console audit logs are empty. After any audited events are performed, you will see the corresponding logs. > - If it has been more than 90 days since console audit logging was disabled, you cannot see any logs. -1. In the upper-right corner of the [TiDB Cloud console](https://tidbcloud.com/), click **Organization** > **Console Audit Logging**. +1. In the lower-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click , and then click **Console Audit Logging**. 2. To get a specific part of audit logs, you can filter the event type, operation status, and time range. 3. (Optional) To filter more fields, click **Advanced filter**, add more filters, and then click **Apply**. 4. Click the row of a log to view its detailed information in the right pane. @@ -45,7 +45,7 @@ You can only view the console audit logs of your organization. To export the console audit logs of your organization, take the following step: -1. In the upper-right corner of the [TiDB Cloud console](https://tidbcloud.com/), click **Organization** > **Console Audit Logging**. +1. In the lower-left corner of the [TiDB Cloud console](https://tidbcloud.com/), click , and then click **Console Audit Logging**. 2. (Optional) If you need to export a specific part of console audit logs, you can filter through various conditions. Otherwise, skip this step. 3. Click **Export** and select the desired export format in JSON or CSV. diff --git a/tidb-cloud/tidb-cloud-encrypt-cmek.md b/tidb-cloud/tidb-cloud-encrypt-cmek.md index 5a841735ac6d9..eb8c9e2580b48 100644 --- a/tidb-cloud/tidb-cloud-encrypt-cmek.md +++ b/tidb-cloud/tidb-cloud-encrypt-cmek.md @@ -17,7 +17,7 @@ After you enable CMEK for a project, all clusters created within this project en - Currently, TiDB Cloud only supports using AWS KMS to provide CMEK. - To use CMEK, you need to enable CMEK when creating a project and complete CMEK-related configurations before creating a cluster. You cannot enable CMEK for existing projects. -- Currently, in CMEK-enabled projects, you can only create [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters hosted on AWS. TiDB Dedicated clusters hosted on GCP and [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters are not supported. +- Currently, in CMEK-enabled projects, you can only create [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters hosted on AWS. TiDB Dedicated clusters hosted on GCP and [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters are not supported. - Currently, for a specific project, you can only enable CMEK for one AWS region. Once you have configured it, you cannot create clusters in other regions within the same project. ## Enable CMEK diff --git a/tidb-cloud/tidb-cloud-events.md b/tidb-cloud/tidb-cloud-events.md index 5c130cad5d49a..2d826782cbeaf 100644 --- a/tidb-cloud/tidb-cloud-events.md +++ b/tidb-cloud/tidb-cloud-events.md @@ -21,7 +21,7 @@ To view the events on the Events page, take the following steps: > **Tip:** > - > If you have multiple projects, you can switch to the target project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of the target cluster. The cluster overview page is displayed. 3. Click **Events** in the left navigation pane. diff --git a/tidb-cloud/tidb-cloud-faq.md b/tidb-cloud/tidb-cloud-faq.md index 637f9eed418b4..9bfe9f530b397 100644 --- a/tidb-cloud/tidb-cloud-faq.md +++ b/tidb-cloud/tidb-cloud-faq.md @@ -41,7 +41,10 @@ No. ### What versions of TiDB are supported on TiDB Cloud? -For the currently supported TiDB version, see [TiDB Cloud Release Notes](/tidb-cloud/tidb-cloud-release-notes.md). +- Starting from June 20, 2023, the default TiDB version for new TiDB Dedicated clusters is v6.5.3. +- Starting from March 7, 2023, the default TiDB version for new TiDB Serverless clusters is v6.6.0. + +For more information, see [TiDB Cloud Release Notes](/tidb-cloud/tidb-cloud-release-notes.md). ### What companies are using TiDB or TiDB Cloud in production? @@ -97,7 +100,7 @@ TiDB is highly compatible with MySQL. You can migrate data from any MySQL-compat ### Does TiDB Cloud support incremental backups? -No. If you need to restore data to any point in time within the cluster's backup retention, you can [use PITR (Point-in-time Recovery)](/tidb-cloud/backup-and-restore.md#automatic-backup). +No. If you need to restore data to any point in time within the cluster's backup retention, you can use PITR (Point-in-time Recovery). For more information, see [Use PITR in a TiDB Dedicated cluster](/tidb-cloud/backup-and-restore.md#automatic-backup) or [Use PITR in a TiDB Serverless cluster](/tidb-cloud/backup-and-restore-serverless.md#restore). ## HTAP FAQs diff --git a/tidb-cloud/tidb-cloud-guide-sample-application-java.md b/tidb-cloud/tidb-cloud-guide-sample-application-java.md index d38edc2b5a64f..66b5b6b64dd7a 100644 --- a/tidb-cloud/tidb-cloud-guide-sample-application-java.md +++ b/tidb-cloud/tidb-cloud-guide-sample-application-java.md @@ -24,7 +24,7 @@ The following introduces how to start a TiDB cluster. **Use a TiDB Serverless cluster** -For detailed steps, see [Create a TiDB Serverless cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-serverless-tier-cluster). +For detailed steps, see [Create a TiDB Serverless cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-serverless-cluster). **Use a local cluster** diff --git a/tidb-cloud/tidb-cloud-htap-quickstart.md b/tidb-cloud/tidb-cloud-htap-quickstart.md index 05b4a02d9b352..0427f7a97a0b6 100644 --- a/tidb-cloud/tidb-cloud-htap-quickstart.md +++ b/tidb-cloud/tidb-cloud-htap-quickstart.md @@ -6,7 +6,7 @@ aliases: ['/tidbcloud/use-htap-cluster'] # TiDB Cloud HTAP Quick Start -[HTAP](https://en.wikipedia.org/wiki/Hybrid_transactional/analytical_processing) means Hybrid Transactional and Analytical Processing. The HTAP cluster in TiDB Cloud is composed of [TiKV](https://tikv.org), a row-based storage engine designed for transactional processing, and [TiFlash](https://docs.pingcap.com/tidb/stable/tiflash-overview), a columnar storage designed for analytical processing. Your application data is first stored in TiKV and then replicated to TiFlash via the Raft consensus algorithm. So it is a real-time replication from the row storage to the columnar storage. +[HTAP](https://en.wikipedia.org/wiki/Hybrid_transactional/analytical_processing) means Hybrid Transactional and Analytical Processing. The HTAP cluster in TiDB Cloud is composed of [TiKV](https://tikv.org), a row-based storage engine designed for transactional processing, and [TiFlash](https://docs.pingcap.com/tidb/stable/tiflash-overview), a columnar storage designed for analytical processing. Your application data is first stored in TiKV and then replicated to TiFlash via the Raft consensus algorithm. So it is a real-time replication from the row-based storage to the columnar storage. This tutorial guides you through an easy way to experience the Hybrid Transactional and Analytical Processing (HTAP) feature of TiDB Cloud. The content includes how to replicate tables to TiFlash, how to run queries with TiFlash, and how to experience the performance boost. diff --git a/tidb-cloud/tidb-cloud-import-local-files.md b/tidb-cloud/tidb-cloud-import-local-files.md index 950517a858be0..c58d83582e71d 100644 --- a/tidb-cloud/tidb-cloud-import-local-files.md +++ b/tidb-cloud/tidb-cloud-import-local-files.md @@ -24,7 +24,7 @@ Currently, this method supports importing one CSV file for one task into either > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click the name of your target cluster to go to its overview page, and then click **Import** in the left navigation pane. diff --git a/tidb-cloud/tidb-cloud-org-sso-authentication.md b/tidb-cloud/tidb-cloud-org-sso-authentication.md index ba2591b52c44d..fd4c215023fa3 100644 --- a/tidb-cloud/tidb-cloud-org-sso-authentication.md +++ b/tidb-cloud/tidb-cloud-org-sso-authentication.md @@ -75,7 +75,7 @@ Before enabling Cloud Organization SSO, make sure to inform your members about t To enable Cloud Organization SSO, take the following steps: 1. Log in to [TiDB Cloud console](https://tidbcloud.com) as a user with the organization owner role. -2. In the upper-right corner of the TiDB Cloud console, click > **Organization Settings**. +2. In the lower-left corner of the TiDB Cloud console, click , and then click **Organization Settings**. 3. On the **Organization Settings** page, click the **Authentication** tab, and then click **Enable**. 4. In the dialog, fill in the custom URL for your organization, which must be unique in TiDB Cloud. diff --git a/tidb-cloud/tidb-cloud-password-authentication.md b/tidb-cloud/tidb-cloud-password-authentication.md index dd7a51deadd6f..56e79b1f1a9e2 100644 --- a/tidb-cloud/tidb-cloud-password-authentication.md +++ b/tidb-cloud/tidb-cloud-password-authentication.md @@ -40,7 +40,7 @@ If the login is successful, you will be directed to the TiDB Cloud console. ### Sign out -In the upper-right corner of the TiDB Cloud console, click **Account** and select **Logout**. +In the lower-left corner of the TiDB Cloud console, click and select **Logout**. ## Password policy @@ -72,7 +72,7 @@ If you forget your password, you can reset it by email as follows: > > If you sign up for TiDB Cloud with email and password, it is recommended that you reset your password every 90 days. Otherwise, you will get a password expiration reminder to change your password when you log in to TiDB Cloud. -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. 2. Click **Account Settings**. @@ -90,9 +90,9 @@ Two-factor authentication adds additional security by requiring an Authenticator ### Enable MFA -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. -2. Click **Account settings**. +2. Click **Account Settings**. 3. Click the **Two Factor Authentication** tab. @@ -100,9 +100,9 @@ Two-factor authentication adds additional security by requiring an Authenticator ### Disable MFA -1. Click **Account** in the upper-right corner of the TiDB Cloud console. +1. Click in the lower-left corner of the TiDB Cloud console. -2. Click **Account settings**. +2. Click **Account Settings**. 3. Click the **Two Factor Authentication** tab. diff --git a/tidb-cloud/tidb-cloud-poc.md b/tidb-cloud/tidb-cloud-poc.md index 1e9b16455398c..5722541e917aa 100644 --- a/tidb-cloud/tidb-cloud-poc.md +++ b/tidb-cloud/tidb-cloud-poc.md @@ -63,7 +63,7 @@ To create a [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) 1. Fill in the PoC application form by doing one of the following: - On the PingCAP website, go to the [Apply for PoC](https://pingcap.com/apply-for-poc/) page to fill in the application form. - - In the [TiDB Cloud console](https://tidbcloud.com/), click **Contact Us** in the upper-right corner, and select **Apply for PoC** to fill in the application form. + - In the [TiDB Cloud console](https://tidbcloud.com/), click **?** in the lower-right corner, click **Request Support**, and then select **Apply for PoC** to fill in the application form. Once you submit the form, the TiDB Cloud Support team will review your application, contact you, and transfer credits to your account once the application is approved. You can also contact a PingCAP support engineer to assist with your PoC procedures to ensure the PoC runs as smoothly as possible. @@ -87,7 +87,7 @@ For a newly created cluster, note the following configurations: Next, you can load your database schemas to the TiDB cluster, including tables and indexes. -Because the amount of PoC credits is limited, to maximize the value of credits, it is recommended that you create a [TiDB Serverless cluster](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) for compatibility tests and preliminary analysis on TiDB Cloud. +Because the amount of PoC credits is limited, to maximize the value of credits, it is recommended that you create a [TiDB Serverless cluster](/tidb-cloud/select-cluster-tier.md#tidb-serverless) for compatibility tests and preliminary analysis on TiDB Cloud. TiDB Cloud is highly compatible with MySQL 5.7. You can directly import your data into TiDB if it is MySQL-compatible or can be adapted to be compatible with MySQL. @@ -216,7 +216,7 @@ To check the credits left for your PoC, go to the [**Clusters**](https://tidbclo ![TiDB Cloud PoC Credits](/media/tidb-cloud/poc-points.png) -Alternatively, you can also click **Account** in the upper-right corner of the TiDB Cloud console, click **Billing**, and click **Credits** to see the credit details page. +Alternatively, you can also click in the lower-left corner of the TiDB Cloud console, click **Billing**, and click **Credits** to see the credit details page. To save credits, remove the cluster that you are not using. Currently, you cannot stop a cluster. You need to ensure that your backups are up to date before removing a cluster, so you can restore the cluster later when you want to resume your PoC. diff --git a/tidb-cloud/tidb-cloud-quickstart.md b/tidb-cloud/tidb-cloud-quickstart.md index f83a53db62cbc..3a77ac14663e1 100644 --- a/tidb-cloud/tidb-cloud-quickstart.md +++ b/tidb-cloud/tidb-cloud-quickstart.md @@ -14,7 +14,7 @@ In addition, you can try out TiDB features on [TiDB Playground](https://play.tid ## Step 1. Create a TiDB cluster -[TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) (Beta) is the best way to get started with TiDB Cloud. To create a TiDB Serverless cluster, take the following steps: +[TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) is the best way to get started with TiDB Cloud. To create a TiDB Serverless cluster, take the following steps: 1. If you do not have a TiDB Cloud account, click [here](https://tidbcloud.com/free-trial) to sign up for an account. diff --git a/tidb-cloud/tidb-cloud-release-notes.md b/tidb-cloud/tidb-cloud-release-notes.md index fd82a5fae2487..08436c665b1e8 100644 --- a/tidb-cloud/tidb-cloud-release-notes.md +++ b/tidb-cloud/tidb-cloud-release-notes.md @@ -8,11 +8,33 @@ aliases: ['/tidbcloud/supported-tidb-versions','/tidbcloud/release-notes'] This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-cloud/) in 2023. +## July 4, 2023 + +**General changes** + +- Support point-in-time recovery (PITR) (beta) for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. + + You can now restore your TiDB Serverless cluster to any point in time within the last 90 days. This feature enhances the data recovery capability of TiDB Serverless clusters. For example, you can use PITR when data write errors occur and you want to restore the data to an earlier state. + + For more information, see [Back up and restore TiDB Serverless data](/tidb-cloud/backup-and-restore-serverless.md#restore). + +**Console changes** + +- Enhance the **Usage This Month** panel on the cluster overview page for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters to provide a clearer view of your current resource usage. + +- Enhance the overall navigation experience by making the following changes: + + - Consolidate **Organization** and **Account** in the upper-right corner into the left navigation bar. + - Consolidate **Admin** in the left navigation bar into **Project** in the left navigation bar, and remove the ☰ hover menu in the upper-left corner. Now you can click to switch between projects and modify project settings. + - Consolidate all the help and support information for TiDB Cloud into the menu of the **?** icon in the lower-right corner, such as documentation, interactive tutorials, self-paced training, and support entries. + +- TiDB Cloud console now supports Dark Mode, which provides a more comfortable, eye-friendly experience. You can switch between light mode and dark mode from the bottom of the left navigation bar. + ## June 27, 2023 **General changes** -- Remove the pre-built sample dataset for newly created [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Remove the pre-built sample dataset for newly created [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. ## June 20, 2023 @@ -36,7 +58,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c For more information, see [Size your cluster](/tidb-cloud/size-your-cluster.md). -- Extend the [monitoring metrics retention period](/tidb-cloud/built-in-monitoring.md#metrics-retention-policy) for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters from 3 days to 7 days. +- Extend the [monitoring metrics retention period](/tidb-cloud/built-in-monitoring.md#metrics-retention-policy) for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters from 3 days to 7 days. By extending the metrics retention period, now you have access to more historical data. This helps you identify trends and patterns of the cluster for better decision-making and faster troubleshooting. @@ -155,7 +177,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c For more information, see [Import CSV Files from Amazon S3 or GCS into TiDB Cloud](/tidb-cloud/import-csv-files.md) and [Import Sample Data](/tidb-cloud/import-sample-data.md). -- Support AWS PrivateLink-powered endpoint connection as a new network access management option for TiDB Cloud [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Support AWS PrivateLink-powered endpoint connection as a new network access management option for TiDB Cloud [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. The private endpoint connection does not expose your data to the public internet. In addition, the endpoint connection supports CIDR overlap and is easier for network management. @@ -167,7 +189,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c To get a full list of the events that can be recorded, see [Logged events](/tidb-cloud/tidb-cloud-events.md#logged-events). -- Introduce the **SQL Statement** tab on the [**SQL Diagnosis**](/tidb-cloud/tune-performance.md) page for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Introduce the **SQL Statement** tab on the [**SQL Diagnosis**](/tidb-cloud/tune-performance.md) page for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. The **SQL Statement** tab provides the following: @@ -181,7 +203,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -- Support directly accessing the [Data Service endpoint](/tidb-cloud/tidb-cloud-glossary.md#endpoint) in the region where a TiDB [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster is located. +- Support directly accessing the [Data Service endpoint](/tidb-cloud/tidb-cloud-glossary.md#endpoint) in the region where a TiDB [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster is located. For newly created Serverless Tier clusters, the endpoint URL now includes the cluster region information. By requesting the regional domain `.data.tidbcloud.com`, you can directly access the endpoint in the region where the TiDB cluster is located. @@ -193,7 +215,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -- For the first five [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters in your organization, TiDB Cloud provides a free usage quota for each of them as follows: +- For the first five [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters in your organization, TiDB Cloud provides a free usage quota for each of them as follows: - Row storage: 5 GiB - [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit): 50 million RUs per month @@ -204,7 +226,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c For more information about the RU consumption of different resources (including read, write, SQL CPU, and network egress), the pricing details, and the throttled information, see [TiDB Cloud Serverless Tier Pricing Details](https://www.pingcap.com/tidb-cloud-serverless-pricing-details). -- Support backup and restore for TiDB Cloud [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Support backup and restore for TiDB Cloud [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. For more information, see [Back up and Restore TiDB Cluster Data](/tidb-cloud/backup-and-restore-serverless.md). @@ -315,7 +337,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - Consolidate the help-related information and actions of TiDB Cloud into a single place. - Now, you can get all the [TiDB Cloud help information](/tidb-cloud/tidb-cloud-support.md#get-help-information) and contact support by clicking **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/). + Now, you can get all the [TiDB Cloud help information](/tidb-cloud/tidb-cloud-support.md) and contact support by clicking **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/). - Introduce the [Getting Started](https://tidbcloud.com/console/getting-started) page to help you learn about TiDB Cloud. @@ -347,7 +369,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c For more information, see [Scale a changefeed](/tidb-cloud/changefeed-overview.md#scale-a-changefeed). -- Support replicating incremental data in real-time from a [Dedicated Tier](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) cluster in AWS to a [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster in the same project and same region. +- Support replicating incremental data in real-time from a [Dedicated Tier](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) cluster in AWS to a [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster in the same project and same region. For more information, see [Sink to TiDB Cloud](/tidb-cloud/changefeed-sink-to-tidb-cloud.md). @@ -359,7 +381,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **Console changes** -- Release a new native web infrastructure for the [Slow Query](/tidb-cloud/tune-performance.md#slow-query) page of [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Release a new native web infrastructure for the [Slow Query](/tidb-cloud/tune-performance.md#slow-query) page of [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. With this new infrastructure, you can easily navigate through the [Slow Query](/tidb-cloud/tune-performance.md#slow-query) page and access the necessary information in a more intuitive and efficient manner. The new infrastructure also resolves many problems on UX, making the SQL diagnosis process more user-friendly. @@ -367,7 +389,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -- Introduce [Data Service (beta)](https://tidbcloud.com/console/data-service) for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters, which enables you to access data via an HTTPS request using a custom API endpoint. +- Introduce [Data Service (beta)](https://tidbcloud.com/console/data-service) for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters, which enables you to access data via an HTTPS request using a custom API endpoint. With Data Service, you can seamlessly integrate TiDB Cloud with any application or service that is compatible with HTTPS. The following are some common scenarios: @@ -402,7 +424,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c For more information, see [TiDB Cloud cluster events](/tidb-cloud/tidb-cloud-events.md). -- Add the **Database Status** tab to the **Monitoring** page for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters, which displays the following database-level metrics: +- Add the **Database Status** tab to the **Monitoring** page for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters, which displays the following database-level metrics: - QPS Per DB - Average Query Duration Per DB @@ -420,7 +442,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - Support modifying column names of the target table to be created by TiDB Cloud when uploading a local CSV file with a header row. - When importing a local CSV file with a header row to a [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster, if you need TiDB Cloud to create the target table and the column names in the header row do not follow the TiDB Cloud column naming conventions, you will see a warning icon next to the corresponding column name. To resolve the warning, you can move the cursor over the icon and follow the message to edit the existing column names or enter new column names. + When importing a local CSV file with a header row to a [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster, if you need TiDB Cloud to create the target table and the column names in the header row do not follow the TiDB Cloud column naming conventions, you will see a warning icon next to the corresponding column name. To resolve the warning, you can move the cursor over the icon and follow the message to edit the existing column names or enter new column names. For information about column naming conventions, see [Import local files](/tidb-cloud/tidb-cloud-import-local-files.md#import-local-files). @@ -428,13 +450,13 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -- Upgrade the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters from [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0) to [v6.6.0](https://docs.pingcap.com/tidb/v6.6/release-6.6.0). +- Upgrade the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters from [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0) to [v6.6.0](https://docs.pingcap.com/tidb/v6.6/release-6.6.0). ## February 28, 2023 **General changes** -- Add the [SQL Diagnosis](/tidb-cloud/tune-performance.md) feature for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Add the [SQL Diagnosis](/tidb-cloud/tune-performance.md) feature for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. With SQL Diagnosis, you can gain deep insights into SQL-related runtime status, which makes the SQL performance tuning more efficient. Currently, the SQL Diagnosis feature for Serverless Tier only provides slow query data. @@ -498,7 +520,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **Console changes** -- Release a new native web infrastructure on the Monitoring page of [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Release a new native web infrastructure on the Monitoring page of [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. With the new infrastructure, you can easily navigate through the Monitoring page and access the necessary information in a more intuitive and efficient manner. The new infrastructure also resolves many problems on UX, making the monitoring process a lot more user-friendly. @@ -520,7 +542,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **Console changes** -- Introduce the **Monitoring** page for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Introduce the **Monitoring** page for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. The **Monitoring** page provides a range of metrics and data, such as the number of SQL statements executed per second, the average duration of queries, and the number of failed queries, which helps you better understand the overall performance of SQL statements in your Serverless Tier cluster. @@ -548,7 +570,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - Upgrade the default TiDB version of new [Dedicated Tier](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters from [v6.1.3](https://docs.pingcap.com/tidb/stable/release-6.1.3) to [v6.5.0](https://docs.pingcap.com/tidb/stable/release-6.5.0). -- For new sign-up users, TiDB Cloud will automatically create a free [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) cluster so that you can quickly start a data exploration journey with TiDB Cloud. +- For new sign-up users, TiDB Cloud will automatically create a free [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) cluster so that you can quickly start a data exploration journey with TiDB Cloud. - Support a new AWS region for [Dedicated Tier](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters: `Seoul (ap-northeast-2)`. @@ -562,7 +584,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **General changes** -- Optimize the feature of importing data from local CSV files to TiDB to improve the user experience for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +- Optimize the feature of importing data from local CSV files to TiDB to improve the user experience for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. - To upload a CSV file, now you can simply drag and drop it to the upload area on the **Import** page. - When creating an import task, if your target database or table does not exist, you can enter a name to let TiDB Cloud create it for you automatically. For the target table to be created, you can specify a primary key or select multiple fields to form a composite primary key. @@ -583,7 +605,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c **Console changes** -- Rename SQL Editor (beta) to Chat2Query (beta) for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters and support generating SQL queries using AI. +- Rename SQL Editor (beta) to Chat2Query (beta) for [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters and support generating SQL queries using AI. In Chat2Query, you can either let AI generate SQL queries automatically or write SQL queries manually, and run SQL queries against databases without a terminal. @@ -609,11 +631,11 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c For more information, see [Use Grafana GUI dashboards to visualize the metrics](/tidb-cloud/monitor-prometheus-and-grafana-integration.md#step-3-use-grafana-gui-dashboards-to-visualize-the-metrics). -- Upgrade the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters from [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0) to [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0). The cold start issue after upgrading the default TiDB version of Serverless Tier clusters to v6.4.0 has been resolved. +- Upgrade the default TiDB version of all [Serverless Tier](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters from [v6.3.0](https://docs.pingcap.com/tidb/v6.3/release-6.3.0) to [v6.4.0](https://docs.pingcap.com/tidb/v6.4/release-6.4.0). The cold start issue after upgrading the default TiDB version of Serverless Tier clusters to v6.4.0 has been resolved. **Console changes** - Simplify the display of the [**Clusters**](https://tidbcloud.com/console/clusters) page and the cluster overview page. - You can click the cluster name on the [**Clusters**](https://tidbcloud.com/console/clusters) page to enter the cluster overview page and start operating the cluster. - - Remove the **Connection** and **Import** panes from the cluster overview page. You can click **Connect** in the upper-right corner to get the connection information and click **Import** in the left navigation pane to import data. \ No newline at end of file + - Remove the **Connection** and **Import** panes from the cluster overview page. You can click **Connect** in the upper-right corner to get the connection information and click **Import** in the left navigation pane to import data. diff --git a/tidb-cloud/tidb-cloud-support.md b/tidb-cloud/tidb-cloud-support.md index f2de948905ef8..931e4a93a18f4 100644 --- a/tidb-cloud/tidb-cloud-support.md +++ b/tidb-cloud/tidb-cloud-support.md @@ -5,51 +5,43 @@ summary: Learn how to contact the support team of TiDB Cloud. # TiDB Cloud Support -TiDB Cloud offers a free basic support plan for each user and you can upgrade to a paid plan for extended services. +The **?** icon in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/) consolidates all the help and support information for TiDB Cloud, such as documentation, interactive tutorials, self-paced training, and support entries. + +## Request PoC, demo, or free trial credits -The information of each support plan is available on the support page of the TiDB Cloud console. To access the page, see [Check or upgrade your support plan](#check-or-upgrade-your-support-plan). +To request a Proof of Concept (PoC), a demo, or free trial credits, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/), and click **Request Support**. > **Tip:** > -> If you want to apply for a PoC, see [Perform a Proof of Concept (PoC) with TiDB Cloud](/tidb-cloud/tidb-cloud-poc.md). - -## Get help information - -Besides documentation, TiDB Cloud provides interactive tutorials and self-paced training to help you get stated quickly. - -To access the help information, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/). +> For more information about PoC, see [Perform a Proof of Concept (PoC) with TiDB Cloud](/tidb-cloud/tidb-cloud-poc.md). -## Request support +## Get support -You can request support for your clusters, projects, and organizations. After receiving your request, the support team will contact you via email. +You can get support for your clusters, projects, and organizations. After receiving your request, the support team will contact you via email. > **Tip:** > > If you want to apply for a beta feature that is available upon request, fill in your application information in the **Description** field of the request. For example, "apply for the xxx feature". -### Request support for a cluster +### Get support for a cluster -You can request support for a cluster in either of the following ways: +You can get support for a cluster in either of the following ways: - On the [**Clusters**](https://tidbcloud.com/console/clusters) page of your project, click **...** in the row of your cluster and select **Get Support**. - On your cluster overview page, click **...** in the upper-right corner and select **Get Support**. -### Request support for a project or organization +### Get support for a project or organization -You can request support for a project or organization in either of the following ways: +To get support for a project or organization, click **?** in the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/), and then click **Chat with Us** or **Create New Case**. -- In the lower-right corner of the [TiDB Cloud console](https://tidbcloud.com/), click **?** and click **Chat with Us**. - -- In the upper-right corner of the [TiDB Cloud console](https://tidbcloud.com/), click **Support** > **Create New Case**. - - You need to provide your organization ID in the request. To find the ID, click **Organization** in the upper-right corner and click **Organization Settings**. +If **Create New Case** is clicked, you also need to provide your organization ID in the request. To find the ID, click in the lower-left corner and click **Organization Settings**. ## Check your submitted request After you have submitted a request, to check the status of your request, perform the following steps: -1. On your TiDB Cloud console, click **Support** in the upper-right corner of the top navigation bar, and click **View Support Plan**. The support page is displayed. +1. In the [TiDB Cloud console](https://tidbcloud.com/), click **?** in the lower-right corner, and then click **View Support Plan**. The support page is displayed. 2. In the **Request Support** area, click **View Support Portal**. The **My request** page is displayed. On the **My request** page, you can view the status of your request. @@ -58,9 +50,11 @@ Alternatively, you can also access the [Customer Support](https://support.pingca ## Check or upgrade your support plan +TiDB Cloud offers a free basic support plan for each user and you can upgrade to a paid plan for extended services. + To check or upgrade your support plan, perform the following steps: -1. On your TiDB Cloud console, click **Support** in the upper-right corner of the top navigation bar, and click **View Support Plan**. +1. In the [TiDB Cloud console](https://tidbcloud.com/), click **?** in the lower-right corner, and then click **View Support Plan**. The support page is displayed. On this page, you can see your **Current Plan**. By default, the **Basic** free plan is selected. @@ -96,5 +90,5 @@ To check or upgrade your support plan, perform the following steps: To downgrade your support plan to **Basic**, perform the following steps: -1. On your TiDB Cloud console, click **Support** in the upper-right corner of the top navigation bar, and click **View Support Plan**. +1. In the [TiDB Cloud console](https://tidbcloud.com/), click **?** in the lower-right corner, and then click **View Support Plan**. 2. At the bottom of the **Support** page, click **Downgrade to basic plan**. diff --git a/tidb-cloud/tune-performance.md b/tidb-cloud/tune-performance.md index 030dd8b866f1b..d7da01d3e9854 100644 --- a/tidb-cloud/tune-performance.md +++ b/tidb-cloud/tune-performance.md @@ -17,7 +17,7 @@ TiDB Cloud provides [Slow Query](#slow-query), [Statement Analysis](#statement-a > **Note:** > -> Currently, **Key Visualizer** and **Index Insight (beta)** are unavailable for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. +> Currently, **Key Visualizer** and **Index Insight (beta)** are unavailable for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. ## Slow Query diff --git a/tidb-cloud/use-chat2query-api.md b/tidb-cloud/use-chat2query-api.md index 4fb0a604aed72..dc72bbfc14b2f 100644 --- a/tidb-cloud/use-chat2query-api.md +++ b/tidb-cloud/use-chat2query-api.md @@ -11,7 +11,7 @@ Chat2Query API can only be accessed through HTTPS, ensuring that all data transm > **Note:** > -> Chat2Query API is available for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless-beta) clusters. To use the Chat2Query API on [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters, contact [TiDB Cloud support](/tidb-cloud/tidb-cloud-support.md). +> Chat2Query API is available for [TiDB Serverless](/tidb-cloud/select-cluster-tier.md#tidb-serverless) clusters. To use the Chat2Query API on [TiDB Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-dedicated) clusters, contact [TiDB Cloud support](/tidb-cloud/tidb-cloud-support.md). ## Before you begin @@ -25,7 +25,7 @@ To enable the Chat2Query API, perform the following steps: > **Tip:** > - > If you have multiple projects, you can view the project list and switch to another project from the ☰ hover menu in the upper-left corner. + > If you have multiple projects, you can click in the lower-left corner and switch to another project. 2. Click your cluster name, and then click **Chat2Query** in the left navigation pane. 3. In the upper-right corner of Chat2Query, click **...** and select **Settings**. diff --git a/tidb-control.md b/tidb-control.md index e19daf80918b5..00417a89a777f 100644 --- a/tidb-control.md +++ b/tidb-control.md @@ -7,6 +7,10 @@ summary: Use TiDB Control to obtain TiDB status information for debugging. TiDB Control is a command-line tool of TiDB, usually used to obtain the status information of TiDB for debugging. This document introduces the features of TiDB Control and how to use these features. +> **Note:** +> +> TiDB Control is specifically designed for debugging purposes and might not be fully compatible with future capabilities introduced in TiDB. It's not recommended to include this tool in applications or utilities development to get information. + ## Get TiDB Control You can get TiDB Control by installing it using TiUP or by compiling it from source code. diff --git a/time-to-live.md b/time-to-live.md index 824d6e102c7fc..377fe1ca9f589 100644 --- a/time-to-live.md +++ b/time-to-live.md @@ -18,7 +18,7 @@ TTL is designed to help users clean up unnecessary data periodically and in a ti > **Warning:** > > This is an experimental feature. It is not recommended that you use it in a production environment. -> TTL is not available for [TiDB Serverless](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-serverless-beta). +> TTL is not available for [TiDB Serverless](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-serverless). ## Syntax