Merge pull request #3149 from ClickHouse/ppv2

Ppv2
ClickHouse · Jan 27, 2025 · 023c8de · 023c8de
2 parents 95b645f + 74d82d5
commit 023c8de
Show file tree

Hide file tree

Showing 119 changed files with 2,676 additions and 922 deletions.
diff --git a/docs/en/_snippets/_add_remote_ip_access_list_detail.md b/docs/en/_snippets/_add_remote_ip_access_list_detail.md
@@ -1,11 +1,11 @@
 <details>
     <summary>Manage your IP Access List</summary>
 
-From your ClickHouse Cloud services list choose the service that you will work with and switch to **Security**.  If the IP Access List does not contain the IP Address or range of the remote system that needs to connect to your ClickHouse Cloud service, then you can resolve the problem with **Add entry**:
+From your ClickHouse Cloud services list choose the service that you will work with and switch to **Settings**.  If the IP Access List does not contain the IP Address or range of the remote system that needs to connect to your ClickHouse Cloud service, then you can resolve the problem with **Add IPs**:
 
 ![Check to see if the service allows traffic](@site/docs/en/_snippets/images/ip-allow-list-check-list.png)
 
-Add the individual IP Address, or the range of addresses that need to connect to your ClickHouse Cloud service. Modify the form as you see fit and then **Add entry** and **Submit entry**.
+Add the individual IP Address, or the range of addresses that need to connect to your ClickHouse Cloud service. Modify the form as you see fit and then **Save**.
 
 ![Add your current IP address](@site/docs/en/_snippets/images/ip-allow-list-add-current-ip.png)
 

diff --git a/docs/en/_snippets/_check_ip_access_list_detail.md b/docs/en/_snippets/_check_ip_access_list_detail.md
diff --git a/docs/en/_snippets/_clickhouse_mysql_cloud_setup.mdx b/docs/en/_snippets/_clickhouse_mysql_cloud_setup.mdx
@@ -1,13 +1,38 @@
-1. After creating your ClickHouse Cloud Service, on the credentials screen, select the MySQL tab
+<br/>
+1. After creating your ClickHouse Cloud Service, on the `Connect your app` screen, select MySQL from the drop down.
+<br/>
+
+<div class="eighty-percent">
 ![Credentials screen - Prompt](./images/mysql1.png)
-2. Toggle the switch to enable the MySQL interface for this specific service. This will expose port `3306` for this service and prompt you with your MySQL connection screen that include your unique MySQL username. The password will be the same as the service's default user password.
+</div>
+
+2. Toggle the switch to enable the MySQL interface for this specific service. This will expose port `3306` for this service and prompt you with your MySQL connection screen that include your unique MySQL username. 
+
+<br/>
+<div class="eighty-percent">
 ![Credentials screen - Enabled MySQL](./images/mysql2.png)
+</div>
+<br/>
+
 Alternatively, in order to enable the MySQL interface for an existing service:
-3. Ensure your service is in `Running` state then click on the "View connection string" button for the service you want to enable the MySQL interface for
+
+3. Ensure your service is in `Running` state then click on the service you want to enable the MySQL interface for. Select "Connect" from the left menu:
+
+<br/>
+<div class="eighty-percent">
 ![Connection screen - Prompt MySQL](./images/mysql3.png)
-4. Toggle the switch to enable the MySQL interface for this specific service. This will prompt you to enter the default password.
+</div>
+<br/>
+
+
+4. Select MySQL from the `Connect With` drop down.
+
+<br/>
 ![Connection screen - Prompt MySQL](./images/mysql4.png)
-5. After entering the password, you will get prompted the MySQL connection string for this service
+<br/>
+
+5. Toggle the switch to enable the MySQL interface for this specific service. This will expose port `3306` for this service and prompt you with your MySQL connection screen that include your unique MySQL username. 
+
 ![Connection screen -  MySQL Enabled](./images/mysql5.png)
 
 ## Creating multiple MySQL users in ClickHouse Cloud

diff --git a/docs/en/_snippets/_cloud_backup.md b/docs/en/_snippets/_cloud_backup.md
diff --git a/docs/en/_snippets/_launch_sql_console.md b/docs/en/_snippets/_launch_sql_console.md
@@ -5,8 +5,12 @@ If you need a SQL client connection, your ClickHouse Cloud service has an associ
 <details>
     <summary>Connect to SQL console</summary>
 
-From your ClickHouse Cloud services list, choose the service that you will work with and click **Connect**.  From here you can **Open SQL console**:
+From your ClickHouse Cloud services list, click on a service. 
 
 ![Connect to SQL Console](@site/docs/en/_snippets/images/cloud-connect-to-sql-console.png)
 
+This will redirect you to the SQL console.
+
+![SQL Console](@site/docs/en/_snippets/images/createservice8.png)
+
 </details>
diff --git a/docs/en/_snippets/_service_actions_menu.md b/docs/en/_snippets/_service_actions_menu.md
@@ -1,3 +1,3 @@
-<p>Open the <b>Actions menu</b> from your ClickHouse Cloud service and choose <b>{props.menu}</b>:</p>
+Select your service, followed by `Data souces` -> `Predefined sample data`.
 
 ![Cloud service Actions menu](@site/docs/en/_snippets/images/cloud-service-actions-menu.png)
diff --git a/docs/en/_snippets/_sign_in_or_trial.md b/docs/en/_snippets/_sign_in_or_trial.md
diff --git a/docs/en/_snippets/images/client_details.png b/docs/en/_snippets/images/client_details.png
diff --git a/docs/en/_snippets/images/cloud-advanced-scaling.png b/docs/en/_snippets/images/cloud-advanced-scaling.png
diff --git a/docs/en/_snippets/images/cloud-backup-list.png b/docs/en/_snippets/images/cloud-backup-list.png
diff --git a/docs/en/_snippets/images/cloud-backup-new-service.png b/docs/en/_snippets/images/cloud-backup-new-service.png
diff --git a/docs/en/_snippets/images/cloud-backup-restore.png b/docs/en/_snippets/images/cloud-backup-restore.png
diff --git a/docs/en/_snippets/images/cloud-connect-to-sql-console.png b/docs/en/_snippets/images/cloud-connect-to-sql-console.png
diff --git a/docs/en/_snippets/images/cloud-load-data-sample.png b/docs/en/_snippets/images/cloud-load-data-sample.png
diff --git a/docs/en/_snippets/images/cloud-select-a-service.png b/docs/en/_snippets/images/cloud-select-a-service.png
diff --git a/docs/en/_snippets/images/cloud-service-actions-menu.png b/docs/en/_snippets/images/cloud-service-actions-menu.png
diff --git a/docs/en/_snippets/images/cloud-service-settings.png b/docs/en/_snippets/images/cloud-service-settings.png
diff --git a/docs/en/_snippets/images/cloud-sign-in-or-trial.png b/docs/en/_snippets/images/cloud-sign-in-or-trial.png
diff --git a/docs/en/_snippets/images/cmek1.png b/docs/en/_snippets/images/cmek1.png
diff --git a/docs/en/_snippets/images/cmek2.png b/docs/en/_snippets/images/cmek2.png
diff --git a/docs/en/_snippets/images/cmek3.png b/docs/en/_snippets/images/cmek3.png
diff --git a/docs/en/_snippets/images/connect1.png b/docs/en/_snippets/images/connect1.png
diff --git a/docs/en/_snippets/images/connect2.png b/docs/en/_snippets/images/connect2.png
diff --git a/docs/en/_snippets/images/connect3.png b/docs/en/_snippets/images/connect3.png
diff --git a/docs/en/_snippets/images/connect4.png b/docs/en/_snippets/images/connect4.png
diff --git a/docs/en/_snippets/images/createservice1.png b/docs/en/_snippets/images/createservice1.png
diff --git a/docs/en/_snippets/images/createservice2.png b/docs/en/_snippets/images/createservice2.png
diff --git a/docs/en/_snippets/images/createservice3.png b/docs/en/_snippets/images/createservice3.png
diff --git a/docs/en/_snippets/images/createservice4.png b/docs/en/_snippets/images/createservice4.png
diff --git a/docs/en/_snippets/images/createservice5.png b/docs/en/_snippets/images/createservice5.png
diff --git a/docs/en/_snippets/images/createservice6.png b/docs/en/_snippets/images/createservice6.png
diff --git a/docs/en/_snippets/images/createservice7.png b/docs/en/_snippets/images/createservice7.png
diff --git a/docs/en/_snippets/images/createservice8.png b/docs/en/_snippets/images/createservice8.png
diff --git a/docs/en/_snippets/images/data_sources.png b/docs/en/_snippets/images/data_sources.png
diff --git a/docs/en/_snippets/images/ip-allow-list-add-current-ip.png b/docs/en/_snippets/images/ip-allow-list-add-current-ip.png
diff --git a/docs/en/_snippets/images/ip-allow-list-check-list.png b/docs/en/_snippets/images/ip-allow-list-check-list.png
diff --git a/docs/en/_snippets/images/mysql1.png b/docs/en/_snippets/images/mysql1.png
diff --git a/docs/en/_snippets/images/mysql2.png b/docs/en/_snippets/images/mysql2.png
diff --git a/docs/en/_snippets/images/mysql3.png b/docs/en/_snippets/images/mysql3.png
diff --git a/docs/en/_snippets/images/mysql4.png b/docs/en/_snippets/images/mysql4.png
diff --git a/docs/en/_snippets/images/mysql5.png b/docs/en/_snippets/images/mysql5.png
diff --git a/docs/en/_snippets/images/new_rows_from_csv.png b/docs/en/_snippets/images/new_rows_from_csv.png
diff --git a/docs/en/_snippets/images/scaling_limits.png b/docs/en/_snippets/images/scaling_limits.png
diff --git a/docs/en/_snippets/images/select_data_source.png b/docs/en/_snippets/images/select_data_source.png
diff --git a/docs/en/_snippets/images/select_plan.png b/docs/en/_snippets/images/select_plan.png
diff --git a/docs/en/_snippets/images/service_connect.png b/docs/en/_snippets/images/service_connect.png
diff --git a/docs/en/_snippets/images/show_databases.png b/docs/en/_snippets/images/show_databases.png
diff --git a/docs/en/_snippets/images/signup_page.png b/docs/en/_snippets/images/signup_page.png
diff --git a/docs/en/about-us/cloud.md b/docs/en/about-us/cloud.md
@@ -21,18 +21,10 @@ Some of the benefits of using ClickHouse Cloud are described below:
 - **Total cost of ownership**: Best price / performance ratio and low administrative overhead.
 - **Broad ecosystem**: Bring your favorite data connectors, visualization tools, SQL and language clients with you.
 
-You can see a walkthrough of how to get started in the video below:
-
-<div class='vimeo-container'>
-
-<iframe width="640" height="360" src="https://www.youtube.com/embed/uWNY0GLUkqc?si=xzj59FEuNxRY7wAb" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-
-</div>
-
 ### What version of ClickHouse does ClickHouse Cloud use?
 
 Clickhouse Cloud continuously upgrades your service to a newer version. After publishing a core database version in the open source, we do additional validation in our cloud staging environment, which typically takes 6-8 weeks before rolling out to production. The rollout is phased out by cloud service provider, service type, and region.
 
-We offer a "Fast" Release Channel for subscribing to updates ahead of the regular release schedule. Access to early upgrades is recommended only for non-production environments and can be requested by logging a support ticket.
+We offer a "Fast" Release Channel for subscribing to updates ahead of the regular release schedule. For more details, see ["Fast Release Channel"](../cloud/manage/upgrades.md/#fast-release-channel-early-upgrades).
 
 If you rely on functionality in the earlier version, you can, in some cases, revert to the previous behavior using your service's compatibility setting.
diff --git a/docs/en/about-us/support.md b/docs/en/about-us/support.md
@@ -7,7 +7,20 @@ sidebar_position: 30
 
 ClickHouse provides Support Services for our ClickHouse Cloud users and customers. Our objective is a Support Services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our Support Services](https://clickhouse.com/support/program/) page.
 
-[Login to the Cloud console](https://clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases.
+[Login to the Cloud console](https://clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. 
+
+**Service level agreements ("SLA")**
+Classification of severity levels for issues reported and response times.
+
+| Severity Level  | Trial                 | Basic                    | Scale                      | Enterprise                                                                             |
+|-----------------|-----------------------|--------------------------|----------------------------|----------------------------------------------------------------------------------------|
+| Severity 1      | Not available         | Not available            | 1 hour 24x7                | 30 minute 24x7                                                                         |
+| Severity 2      | Not available         | Not available            | 4 business hours           | 2 business hours                                                                       |
+| Severity 3      | 1 business day        | 1 business day           | 1 business day             | 1 business day                                                                         | 
+
+(*) Business hours are Monday 00:00 UTC to Saturday 00:00 UTC
+
+Customers can only log Severity 3 tickets for single replica services across tiers. The exception is for a service leveraging the compute-compute separation feature, where the parent service is running 3+ replicas.
 
 You can also subscribe to our [status page](https://status.clickhouse.com) to get notified quickly about any incidents affecting our platform.
 

diff --git a/docs/en/cloud/bestpractices/usagelimits.md b/docs/en/cloud/bestpractices/usagelimits.md
@@ -13,13 +13,19 @@ If you've reached one of those limits, it may mean that you are implementing you
 :::
 
 # Tables
-Clickhouse Cloud have a limit of **5 000** tables per instance
+Clickhouse Cloud have a limit of **5000** tables per instance
 
 # Databases
-Clickhouse Cloud have a limit of **1 000** databases per instance
+Clickhouse Cloud have a limit of **1000** databases per instance
 
 # Partitions
-Clickhouse Cloud have a limit of **50 000** [partitions](https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/custom-partitioning-key) per instance
+Clickhouse Cloud have a limit of **50000** [partitions](https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/custom-partitioning-key) per instance
 
 # Parts
-Clickhouse Cloud have a limit of **100 000** [parts](https://clickhouse.com/docs/en/operations/system-tables/parts) per instance
+Clickhouse Cloud have a limit of **100000** [parts](https://clickhouse.com/docs/en/operations/system-tables/parts) per instance
+
+:::note
+For Single Replica Services, the maximum number of Databases is restricted to 100, and the maximum number of Tables is restricted to 500. In addition, Storage for Basic Tier Services is limited to 1 TB.
+:::
+
+