Merge branch 'cloudflare:production' into production

Author: Thienlta

public/__redirects

@@ -2045,9 +2045,12 @@
 /version-management/reference/available-settings/ /version-management/reference/available-configurations/ 301
 
 # hyperdrive
-/hyperdrive/learning/how-hyperdrive-works/ /hyperdrive/configuration/how-hyperdrive-works/ 301
+/hyperdrive/configuration/how-hyperdrive-works/ /hyperdrive/concepts/how-hyperdrive-works/ 301
+/hyperdrive/configuration/query-caching/ /hyperdrive/concepts/query-caching/ 301
+/hyperdrive/configuration/connection-pooling/ /hyperdrive/concepts/connection-pooling/ 301
+/hyperdrive/learning/how-hyperdrive-works/ /hyperdrive/concepts/how-hyperdrive-works/ 301
 /hyperdrive/learning/connect-to-postgres/ /hyperdrive/examples/connect-to-postgres/ 301
-/hyperdrive/learning/query-caching/ /hyperdrive/configuration/query-caching/ 301
+/hyperdrive/learning/query-caching/ /hyperdrive/concepts/query-caching/ 301
 /hyperdrive/learning/troubleshooting/ /hyperdrive/observability/troubleshooting/ 301
 /hyperdrive/changelog/ /hyperdrive/platform/release-notes/ 301
 /hyperdrive/platform/changelog/ /hyperdrive/platform/release-notes/ 301

src/assets/images/hyperdrive/configuration/hyperdrive-connection-lifecycle.svg

@@ -18,4 +18,4 @@ _P50, P75, and P90 Hyperdrive session latency for all client connection sessions
 
 This performance improvement is applied to all new and existing Hyperdrive configurations that have caching enabled.
 
-For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](/hyperdrive/configuration/how-hyperdrive-works/#query-caching).
+For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](/hyperdrive/concepts/how-hyperdrive-works/#query-caching).

src/assets/images/logs/Health-Dashboard.gif

@@ -14,6 +14,6 @@ By improving placement of Hyperdrive database connection pools, Workers' Smart P
 
 With this update, Hyperdrive also uses [Cloudflare's standard IP address ranges](https://www.cloudflare.com/ips/) to connect to your database. This enables you to configure the firewall policies (IP access control lists) of your database to only allow access from Cloudflare and Hyperdrive.
 
-Refer to [documentation on how Hyperdrive makes connecting to regional databases from Cloudflare Workers fast](/hyperdrive/configuration/how-hyperdrive-works/).
+Refer to [documentation on how Hyperdrive makes connecting to regional databases from Cloudflare Workers fast](/hyperdrive/concepts/how-hyperdrive-works/).
 
 This improvement is enabled on all Hyperdrive configurations.

src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx

@@ -46,4 +46,4 @@ export default {
 } satisfies ExportedHandler<Env>;
 ```
 
-Learn more about [how Hyperdrive works](/hyperdrive/configuration/how-hyperdrive-works/) and [get started building Workers that connect to MySQL with Hyperdrive](/hyperdrive/get-started/).
+Learn more about [how Hyperdrive works](/hyperdrive/concepts/how-hyperdrive-works/) and [get started building Workers that connect to MySQL with Hyperdrive](/hyperdrive/get-started/).

src/content/changelog/hyperdrive/2025-03-04-hyperdrive-pooling-near-database-and-ip-range-egress.mdx

@@ -12,4 +12,4 @@ All configurations have a minimum of 5 connections. The maximum connection count
 
 This feature allows you to right-size your connection pool based on your database capacity and application requirements. You can configure connection counts through the Cloudflare dashboard or API.
 
-Refer to the [Hyperdrive configuration documentation](/hyperdrive/configuration/connection-pooling/) for more information.
+Refer to the [Hyperdrive configuration documentation](/hyperdrive/concepts/connection-pooling/) for more information.

src/content/changelog/hyperdrive/2025-04-08-hyperdrive-mysql-support.mdx

@@ -0,0 +1,15 @@
+---
+title: Logpush Health Dashboards
+description: Introducing Logpush Health Dashboards
+date: 2025-11-11
+---
+
+We’re excited to introduce **Logpush Health Dashboards**, giving customers real-time visibility into the status, reliability, and performance of their [Logpush](/logs/logpush/) jobs. Health dashboards make it easier to detect delivery issues, monitor job stability, and track performance across destinations. The dashboards are divided into two sections:
+
+- **Upload Health**: See how much data was successfully uploaded, where drops occurred, and how your jobs are performing overall. This includes data completeness, success rate, and upload volume.
+
+- **Upload Reliability** – Diagnose issues impacting stability, retries, or latency, and monitor key metrics such as retry counts, upload duration, and destination availability.
+
+![Health Dashboard](src/assets/images/logs/Health-Dashboard.gif)
+
+Health Dashboards can be accessed from the Logpush page in the Cloudflare dashboard at the account or zone level, under the Health tab. For more details, refer to our [**Logpush Health Dashboards**](/logs/logpush/logpush-health) documentation, which includes a comprehensive troubleshooting guide to help interpret and resolve common issues.

src/content/changelog/hyperdrive/2025-07-02-hyperdrive-configurable-connection-count.mdx

@@ -10,7 +10,7 @@ head:
 
 import { Stream } from "~/components";
 
-The [Cloudflare China Network](https://www.cloudflare.com/china-network/) is a package of selected Cloudflare's performance and security products running on data centers located in Mainland China and operated by Cloudflare's partner JD Cloud.
+The [Cloudflare China Network](https://www.cloudflare.com/application-services/products/china-network/) is a package of selected Cloudflare's performance and security products running on data centers located in Mainland China and operated by Cloudflare's partner JD Cloud.
 
 The data centers cover most populated regions in China. Combining Cloudflare's technological leadership and JD Cloud's local operations expertise, the Cloudflare China Network is designed to meet the needs for secure, reliable, and fast-performing content delivery in China. You can use the same configurations that you use with Cloudflare everywhere else in the world and with the same dashboard experience.
 

src/content/changelog/logs/2025-11-11-health-dashboards.mdx

@@ -10,6 +10,10 @@ import { Render, DashButton, Steps } from "~/components";
 
 A `cf_clearance` cookie proves to Cloudflare that the visitor is a verified human and has passed the Challenge presented to them. 
 
+The `cf_clearance` cookie is securely tied to the specific visitor and device it was issued to. This binding is a security feature designed to prevent the cookie from being easily transferred and re-used on other machines.
+
+As an additional layer of security, Cloudflare recommends that customers [add a rate limiting rule](/waf/rate-limiting-rules/) based on the `cf_clearance` cookie value. This ensures that a single, valid cookie cannot be abused by a single machine to send an excessive volume of requests.
+
 If a visitor passes an Interactive Challenge (highest security level), then the `cf_clearance` cookie indicates this to the origin and allows the visitor to bypass any other Challenge on the website, whether it is another Interactive Challenge, a Managed Challenge, or a non-interactive JavaScript Challenge for as long as the cookie is valid.
 
 If a visitor receives a `cf_clearance` cookie on a page that uses a WAF rule with Managed or JavaScript Challenge (lower security levels), then encountering a different page with a higher security clearance level Challenge will prompt them to solve the Challenge again.
@@ -98,4 +102,4 @@ For more details on managing hostnames, refer to the [Hostname Management docume
   3. Under **Would you like to opt for pre-clearance for this site?** select **Yes**.
   4. Choose the pre-clearance level from the select box.
   5. Select **Update**.
-</Steps>
+</Steps>