add content for clinic us server (#9566) (#9578)

TOC.md

@@ -332,7 +332,7 @@
       - [tiup-cluster](/tiup/tiup-cluster.md)
       - [tiup-mirror](/tiup/tiup-mirror.md)
       - [tiup-bench](/tiup/tiup-bench.md)
-  - PingCAP Clinic Diagnostic Service (Technical Preview)
+  - PingCAP Clinic Diagnostic Service
     - [Overview](/clinic/clinic-introduction.md)
     - [Quick Start](/clinic/quick-start-with-clinic.md)
     - [Troubleshoot TiDB Cluster Using PingCAP Clinic](/clinic/clinic-user-guide-for-tiup.md)

clinic/clinic-data-instruction-for-tiup.md

@@ -9,11 +9,10 @@ This document provides the types of diagnostic data that can be collected by Pin
 
 The diagnostic data collected by PingCAP Clinic is **only** used for troubleshooting cluster problems.
 
-Clinic Server is a diagnostic service deployed in the cloud. Currently, you can upload the collected diagnostic data to [Clinic Server China](https://clinic.pingcap.com.cn) only. The uploaded data is stored in the AWS S3 China (Beijing) region server set up by PingCAP. Clinic Server Global will be provided soon with a new URL and data storage location. For details, see [PingCAP Clinic components](/clinic/clinic-introduction.md).
+A diagnostic service deployed in the cloud, Clinic Server provides two independent services depending on the data storage location:
 
-PingCAP strictly controls permissions for data access and only allows authorized in-house technical support staff to access the uploaded data.
-
-After a technical support case is closed, PingCAP permanently deletes or anonymizes the corresponding data within 90 days.
+- [Clinic Server in the US](https://clinic.pingcap.com): If you upload the collected data to Clinic Server in the US, the data will be stored in the Amazon S3 service deployed by PingCAP in AWS US regions. PingCAP uses strict data access policies and only authorized technical support can access the data.
+- [Clinic Server in the Chinese mainland](https://clinic.pingcap.com.cn): If you upload the collected data to Clinic Server in the Chinese mainland, the data will be stored in the Amazon S3 service deployed by PingCAP in China (Beijing) regions. PingCAP uses strict data access policies and only authorized technical support can access the data.
 
 ## TiDB clusters
 

clinic/clinic-introduction.md

@@ -7,31 +7,32 @@ summary: Learn about the PingCAP Clinic Diagnostic Service (PingCAP Clinic), inc
 
 PingCAP Clinic Diagnostic Service (PingCAP Clinic) is a diagnostic service provided by PingCAP for TiDB clusters that are deployed using either TiUP or TiDB Operator. This service helps to troubleshoot cluster problems remotely and provides a quick check of cluster status locally. With PingCAP Clinic, you can ensure the stable operation of your TiDB cluster for its full life-cycle, predict potential problems, reduce the probability of problems, troubleshoot cluster problems quickly, and fix cluster problems.
 
-PingCAP Clinic is currently in the Technical Preview stage. This service provides the following two components to diagnose cluster problems:
+PingCAP Clinic provides the following two components to diagnose cluster problems:
 
 - Diag client:
 
     Diag client (Diag) is a diagnostic tool deployed on the cluster side. Diag is used to collect cluster diagnostic data, upload diagnostic data to the Clinic Server, and perform a quick health check locally on your cluster. For a full list of diagnostic data that can be collected by Diag, see [PingCAP Clinic Diagnostic Data](/clinic/clinic-data-instruction-for-tiup.md).
 
     > **Note:**
     >
-    > Diag temporarily **does not support** collecting data from the clusters deployed using TiDB Ansible.
+    > Diag supports TiDB v4.0 and later versions, but **does not support** collecting data from clusters deployed using TiDB Ansible.
 
 - Clinic Server:
 
-    Clinic Server is a cloud service deployed in the cloud. By providing diagnostic services in the SaaS model, the Clinic Server can not only receive uploaded diagnostic data but also work as an online diagnostic environment to store data, view data, and provide cluster diagnostic reports.
+    Clinic Server is a cloud service deployed in the cloud. By providing diagnostic services in the SaaS model, the Clinic Server can not only receive uploaded diagnostic data but also work as an online diagnostic environment to store data, view data, and provide cluster diagnostic reports. Clinic Server provides two independent services depending on the storage location:
 
-    Currently, you can upload the collected diagnostic data to [Clinic Server China](https://clinic.pingcap.com.cn) only. The uploaded data is stored in the AWS S3 China (Beijing) region server set up by PingCAP. Clinic Server Global will be provided soon with a new URL and data storage location in one of the AWS S3 regions in North America.
+    - [Clinic Server in the US](https://clinic.pingcap.com): Data is stored in AWS in US.
+    - [Clinic Server in the Chinese mainland](https://clinic.pingcap.com.cn): Data is stored in AWS in China (Beijing) regions.
 
 ## User scenarios
 
 - Troubleshoot cluster problems remotely
 
     When your cluster has some problems that cannot be fixed quickly, you can ask for help at [TiDB Community slack channel](https://tidbcommunity.slack.com/archives/CH7TTLL7P) or contact PingCAP technical support. When contacting technical support for remote assistance, you need to save various diagnostic data from the cluster and forward the data to the support staff. In this case, you can use Diag to collect diagnostic data with one click. Diag helps you to collect complete diagnostic data quickly, which can avoid complex manual data collection operations. After collecting data, you can upload the data to the Clinic Server for PingCAP technical support staff to troubleshoot cluster problems. The Clinic Server provides secure storage for uploaded diagnostic data and supports the online diagnosis, which greatly improves the troubleshooting efficiency.
 
-- Perform a quick check on the cluster status locally
+- Quickly check cluster status
 
-    Even if your cluster runs stably now, it is necessary to periodically check the cluster to avoid potential stability risks. You can check the potential health risks of a cluster using the local quick check feature provided by PingCAP Clinic. The PingCAP Clinic Technical Preview version provides a rationality check on cluster configuration items to discover unreasonable configurations and provide modification suggestions.
+    Even if your cluster is running stably for now, it is necessary to periodically check the cluster to detect potential stability risks. You can identify potential health risks of a cluster using the local and server-side quick check feature provided by PingCAP Clinic.
 
 ## Implementation principles
 
@@ -41,11 +42,11 @@ First, Diag gets cluster topology information from the deployment tool TiUP (tiu
 
 - Transfer server files through SCP
 
-    For the clusters deployed using TiUP, Diag can collect log files and configuration files directly from the nodes of the target component through the Secure copy protocol (SCP).
+    For clusters deployed using TiUP, Diag can collect log files and configuration files directly from the nodes of the target component through the Secure copy protocol (SCP).
 
 - Collect data by running commands remotely through SSH
 
-    For the clusters deployed using TiUP, Diag can connect to the target component system through SSH (Secure Shell) and run commands (such as Insight) to obtain system information, including kernel logs, kernel parameters, and basic information of the system and hardware.
+    For clusters deployed using TiUP, Diag can connect to the target component system through SSH (Secure Shell) and run commands (such as Insight) to obtain system information, including kernel logs, kernel parameters, and basic information of the system and hardware.
 
 - Collect data through HTTP call
 
@@ -56,6 +57,21 @@ First, Diag gets cluster topology information from the deployment tool TiUP (tiu
 
     Using SQL statements, Diag can query system variables and other information of TiDB. To use this method, you need to **additionally provide** the username and password to access TiDB when collecting data.
 
+## The limitations of Clinic Server
+
+> **Note:**
+>
+> - Clinic Server is free from July 15, 2022 to Jan 14, 2023. You will be notified through email before Jan 14, 2023 if the service starts charging fee afterwards.
+> - If you want to adjust the usage limitations, contact PingCAP technical support.
+
+| Service Type| Limitation |
+| :------ | :------ |
+| Number of clusters | 10/organization |
+| Storage capacity | 50 GB/cluster |
+| Storage duration | 180 days |
+| Data size | 3 GB/package |
+| Saving duration of the data rebuild environment | 3 days |
+
 ## Next step
 
 - Use PingCAP Clinic in an on-premise environment