Merge main and fix conflict

Author: Blargian

.gitignore

@@ -50,6 +50,10 @@ docs/cloud/manage/api/prometheus-api-reference.md
 docs/cloud/manage/api/usageCost-api-reference.md
 docs/whats-new/changelog/index.md
 docs/about-us/beta-and-experimental-features.md
+static/knowledgebase_toc.json
+.floating-pages-validation-failed
+.frontmatter-validation-failed
+logs/
 
 .vscode
 .aspell.en.prepl
@@ -59,8 +63,8 @@ docs/about-us/beta-and-experimental-features.md
 **.translate
 /ClickHouse/
 
-
 # Ignore table of contents files
 docs/cloud/reference/release-notes-index.md
 docs/whats-new/changelog/index.md
-docs/cloud/manage/api/api-reference-index.md
+docs/cloud/manage/api/api-reference-index.md
+docs/getting-started/index.md

docs/about-us/beta-and-experimental-features.md

@@ -38,3 +38,10 @@ Note: please be sure to be using a current version of the ClickHouse [compatibil
 - Cannot be enabled in the cloud
 
 Please note: no additional experimental features are allowed to be enabled in ClickHouse Cloud other than those listed above as Beta.
+
+<!-- The inner content of the tags below are replaced at build time with a table generated from source
+     Please do not modify or remove the tags
+-->
+
+<!--AUTOGENERATED_START-->
+<!--AUTOGENERATED_END-->

docs/architecture/cluster-deployment.md

@@ -6,7 +6,7 @@ title: 'Cluster Deployment'
 description: 'By going through this tutorial, you will learn how to set up a simple ClickHouse cluster.'
 ---
 
-This tutorial assumes you've already set up a [local ClickHouse server](../getting-started/install.md)
+This tutorial assumes you've already set up a [local ClickHouse server](../getting-started/install/install.mdx)
 
 By going through this tutorial, you'll learn how to set up a simple ClickHouse cluster. It'll be small, but fault-tolerant and scalable. Then we will use one of the example datasets to fill it with data and execute some demo queries.
 

docs/guides/sizing-and-hardware-recommendations.md renamed to docs/best-practices/sizing-and-hardware-recommendations.md

@@ -69,7 +69,14 @@ As an example, when using M-type CPUs, we recommend provisioning 100GB of memory
 
 ## Memory {#memory}
 
-Like your choice of CPU, your choice of memory to storage ratio and memory to CPU ratio is dependent on your case. In general, however, the more memory you have, the faster your queries will run. If your use case is sensitive to price, lower amounts of memory will work as it is possible to enable settings ([`max_bytes_before_external_group_by`](/operations/settings/settings#max_bytes_before_external_group_by) and [`max_bytes_before_external_sort`](/operations/settings/settings#max_bytes_before_external_sort)) to allow spilling data to disk, but note that this may significantly affect query performance.
+Like your choice of CPU, your choice of memory to storage ratio and memory to CPU ratio is dependent on your use-case.
+
+The required volume of RAM generally depends on:
+- The complexity of queries.
+- The amount of data that is processed in queries.
+
+In general, however, the more memory you have, the faster your queries will run. 
+If your use case is sensitive to price, lower amounts of memory will work as it is possible to enable settings ([`max_bytes_before_external_group_by`](/operations/settings/settings#max_bytes_before_external_group_by) and [`max_bytes_before_external_sort`](/operations/settings/settings#max_bytes_before_external_sort)) to allow spilling data to disk, but note that this may significantly affect query performance.
 
 ### What should the memory to storage ratio be? {#what-should-the-memory-to-storage-ratio-be}
 

docs/cloud/manage/backups/export-backups-to-own-cloud-account.md

@@ -97,10 +97,6 @@ See: [Configuring BACKUP/RESTORE to use an S3 Endpoint](/operations/backup#confi
 
 ## Backup / Restore to Azure Blob Storage {#backup--restore-to-azure-blob-storage}
 
-:::note
-Exporting backups to you own bucket on Azure Blob Storage is not available yet. We will update this page when the feature is available.
-:::
-
 ### Take a DB Backup {#take-a-db-backup-1}
 
 **Full Backup**

docs/cloud/manage/openapi.md

@@ -17,7 +17,7 @@ import Image from '@theme/IdealImage';
 ClickHouse Cloud provides an API utilizing OpenAPI that allows you to programmatically manage your account and aspects of your services.
 
 :::note
-This document covers the ClickHouse Cloud API. For database API endpoints, please see [Cloud Endpoints API](//cloud/get-started/query-endpoints.md)
+This document covers the ClickHouse Cloud API. For database API endpoints, please see [Cloud Endpoints API](/cloud/get-started/query-endpoints.md)
 :::
 
 1. You can use the **API Keys** tab on the left menu to create and manage your API keys.

docs/cloud/manage/troubleshooting-billing-issues.md

@@ -1,14 +1,14 @@
 ---
 sidebar_label: 'Troubleshooting Billing Issues'
 slug: /manage/troubleshooting-billing-issues
-title: 'Troubleshooting Billing Issues'
+title: 'Troubleshooting billing issues'
 description: 'Troubleshooting article for common billing issues'
 ---
 
 import trial_expired from '@site/static/images/cloud/manage/trial-expired.png';
 import Image from '@theme/IdealImage';
 
-# Troubleshooting Billing Issues
+# Troubleshooting billing issues
 
 ## Fixing non-working payment details {#fixing-non-working-payment-details}
 

docs/cloud/reference/byoc.md

@@ -24,7 +24,7 @@ BYOC (Bring Your Own Cloud) allows you to deploy ClickHouse Cloud on your own cl
 
 **If you would like access, please [contact us](https://clickhouse.com/cloud/bring-your-own-cloud).** Refer to our [Terms of Service](https://clickhouse.com/legal/agreements/terms-of-service) for additional information.
 
-BYOC is currently only supported for AWS, with GCP and Microsoft Azure in development.
+BYOC is currently only supported for AWS. You can join the wait list for GCP and Azure [here](https://clickhouse.com/cloud/bring-your-own-cloud).
 
 :::note 
 BYOC is designed specifically for large-scale deployments, and requires customers to sign a committed contract.

docs/cloud/reference/changelog.md

@@ -30,6 +30,21 @@ import query_endpoints from '@site/static/images/cloud/reference/may-17-query-en
 
 In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibility](/cloud/reference/cloud-compatibility.md) page.
 
+## May 16, 2025 {#may-16-2025}
+
+- Introduced the Resource Utilization Dashboard which provides a view of 
+  resources being used by a service in ClickHouse Cloud. The following metrics 
+  are scraped from system tables, and displayed on this dashboard:
+  * Memory & CPU: Graphs for `CGroupMemoryTotal` (Allocated Memory), `CGroupMaxCPU` (allocated CPU),
+    `MemoryResident` (memory used), and `ProfileEvent_OSCPUVirtualTimeMicroseconds` (CPU used)
+  * Data Transfer: Graphs showing data ingress and egress from ClickHouse Cloud. Learn more [here](/cloud/manage/network-data-transfer).
+- We’re excited to announce the launch of our new ClickHouse Cloud Prometheus/Grafana mix-in, 
+  built to simplify monitoring for your ClickHouse Cloud services.
+  This mix-in uses our Prometheus-compatible API endpoint to seamlessly integrate
+  ClickHouse metrics into your existing Prometheus and Grafana setup. It includes
+  a pre-configured dashboard that gives you real-time visibility into the health 
+  and performance of your services. Refer to the launch [blog](https://clickhouse.com/blog/monitor-with-new-prometheus-grafana-mix-in) to read more.
+
 ## April 18, 2025 {#april-18-2025}
 
 - Introduced a new **Member** organization level role and two new service level 

docs/cloud/reference/warehouses.md

@@ -45,7 +45,7 @@ Each compute node group will have its own endpoint so you can choose which set o
 
 _Fig. 2 - compute separation in ClickHouse Cloud_
 
-In this private preview program, you will have the ability to create extra services that share the same data with your existing services, or create a completely new setup with multiple services sharing the same data.
+It is possible to create extra services that share the same data with your existing services, or create a completely new setup with multiple services sharing the same data.
 
 ## What is a Warehouse? {#what-is-a-warehouse}
 
@@ -122,8 +122,6 @@ Once compute-compute is enabled for a service (at least one secondary service wa
 
 ## Limitations {#limitations}
 
-Because this compute-compute separation is currently in private preview, there are some limitations to using this feature. Most of these limitations will be removed once the feature is released to GA (general availability):
-
 1. **Primary service should always be up and should not be idled (limitation will be removed some time after GA).** During the private preview and some time after GA, the primary service (usually the existing service that you want to extend by adding other services) will be always up and will have the idling setting disabled. You will not be able to stop or idle the primary service if there is at least one secondary service. Once all secondary services are removed, you can stop or idle the original service again.
 
 2. **Sometimes workloads cannot be isolated.** Though the goal is to give you an option to isolate database workloads from each other, there can be corner cases where one workload in one service will affect another service sharing the same data. These are quite rare situations that are mostly connected to OLTP-like workloads.
@@ -146,7 +144,7 @@ settings distributed_ddl_task_timeout=0
 
 ## Pricing {#pricing}
 
-Extra services created during the private preview are billed as usual. Compute prices are the same for all services in a warehouse (primary and secondary). Storage is billed only once - it is included in the first (original) service.
+Compute prices are the same for all services in a warehouse (primary and secondary). Storage is billed only once - it is included in the first (original) service.
 
 ## Backups {#backups}