Merge branch 'production' into marcio/pcx17803-mconn-kvm

Author: marciocloudflare

package-lock.json

@@ -35,7 +35,7 @@
 		"@astrojs/starlight": "0.34.3",
 		"@astrojs/starlight-docsearch": "0.6.0",
 		"@astrojs/starlight-tailwind": "4.0.1",
-		"@cloudflare/vitest-pool-workers": "0.8.48",
+		"@cloudflare/vitest-pool-workers": "0.8.50",
 		"@cloudflare/workers-types": "4.20250703.0",
 		"@codingheads/sticky-header": "1.0.2",
 		"@expressive-code/plugin-collapsible-sections": "0.41.2",
@@ -127,7 +127,7 @@
 		"ts-blank-space": "0.6.1",
 		"tsx": "4.20.3",
 		"typescript": "5.8.3",
-		"typescript-eslint": "8.35.0",
+		"typescript-eslint": "8.36.0",
 		"unified": "11.0.5",
 		"unist-util-visit": "5.0.0",
 		"vite-tsconfig-paths": "5.1.4",

package.json

@@ -1004,7 +1004,7 @@
 # magic-wan
 /magic-wan/tutorials/ipsec/ /magic-wan/reference/tunnels/#ipsec-tunnels 301
 /magic-wan/how-to/configure-tunnels/ /magic-wan/configuration/manually/how-to/configure-tunnels/ 301
-/magic-wan/about/ /magic-wan/reference/ 301
+/magic-wan/about/ /magic-wan/get-started/ 301
 /magic-wan/about/traffic-steering/ /magic-wan/reference/traffic-steering/ 301
 /magic-wan/how-to/ipsec/ /magic-wan/reference/tunnels/#ipsec-tunnels 301
 /magic-wan/partners/aruba-edgeconnect/ /magic-wan/configuration/manually/third-party/aruba-edgeconnect/ 301
@@ -1022,7 +1022,6 @@
 /magic-wan/configuration/manually/how-to/view-analytics/ /magic-wan/analytics/ 301
 /magic-wan/configuration/common-settings/view-analytics/ /magic-wan/analytics/ 301
 /magic-wan/prerequisites/ /magic-wan/get-started/ 301
-/magic-wan/configuration/common-settings/check-tunnel-health-dashboard/ /magic-wan/configuration/common-settings/tunnel-health-checks/ 301
 /magic-wan/configuration/manually/how-to/configure-static-routes/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
 /magic-wan/configuration/manually/how-to/bgp-peering/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
 

public/__redirects

@@ -1,9 +1,8 @@
 ---
-pcx_content_type: how-to
+pcx_content_type: tutorial
 title: Datadog
 sidebar:
   order: 98
-
 ---
 
 This tutorial explains how to analyze Cloudflare metrics using the [Cloudflare Integration tile for Datadog](https://docs.datadoghq.com/integrations/cloudflare/).
@@ -12,10 +11,10 @@ This tutorial explains how to analyze Cloudflare metrics using the [Cloudflare I
 
 Before viewing the Cloudflare dashboard in Datadog, note that this integration:
 
-* Is available to all Cloudflare customer plans (Free, Pro, Business and Enterprise)
-* Is based on the Cloudflare Analytics API
-* Provides Cloudflare web traffic and DNS metrics only
-* Does not feature data coming from request logs stored in Cloudflare Logs
+- Is available to all Cloudflare customer plans (Free, Pro, Business and Enterprise)
+- Is based on the Cloudflare Analytics API
+- Provides Cloudflare web traffic and DNS metrics only
+- Does not feature data coming from request logs stored in Cloudflare Logs
 
 ## Task 1 - Install the Cloudflare App
 
@@ -25,18 +24,18 @@ To install the Cloudflare App for Datadog:
 
 2. Click the **Integrations** tab.
 
-3. In the **search box**, start typing *Cloudflare*. The app tile should appear below the search box.
+3. In the **search box**, start typing _Cloudflare_. The app tile should appear below the search box.
    ![Searching for Cloudflare App in the Datadog Integrations tab](~/assets/images/fundamentals/datadog/screenshots/datadog-integrations.png)
 
 4. Click the **Cloudflare** tile to begin the installation.
 
 5. Next, click **Configuration** and then complete the following:
 
-   * **Account name**: (Optional) This can be any value. It has not impact on the site data pulled from Cloudflare.
+   - **Account name**: (Optional) This can be any value. It has not impact on the site data pulled from Cloudflare.
 
-   * **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [*Analytics* role](/fundamentals/manage-members/roles/) (read-only). Note that the *Analytics* role is available to Enterprise customers only.
+   - **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [_Analytics_ role](/fundamentals/manage-members/roles/) (read-only). Note that the _Analytics_ role is available to Enterprise customers only.
 
-   * **API Key**: Enter your Cloudflare Global API key. For details refer to [API Keys](/fundamentals/api/get-started/keys/).
+   - **API Key**: Enter your Cloudflare Global API key. For details refer to [API Keys](/fundamentals/api/get-started/keys/).
 
 6. Click **Install Integration**.
    ![Configuring and installing the Datadog integration](~/assets/images/fundamentals/datadog/screenshots/cloudflare-tile-datadog-fill-details.png)
@@ -49,13 +48,13 @@ By default, the dashboard displays metrics for all sites in your Cloudflare acco
 
 The dashboard displays the following metrics:
 
-* **Threats** (threats by type, threats by country)
-* **Requests** (total requests, cached requests, uncached requests, top countries by request, requests by IP class, top content types)
-* **Bandwidth** (total bandwidth, encrypted and unencrypted traffic cached bandwidth, uncached bandwidth)
-* **Caching** (Cache hit rate, request caching rate over time)
-* **HTTP response status errors**
-* **Page views**
-* **Search Engine Bot Traffic**
-* **DNS** (DNS queries, response time, top hostnames, queries by type, stale vs. uncached queries)
+- **Threats** (threats by type, threats by country)
+- **Requests** (total requests, cached requests, uncached requests, top countries by request, requests by IP class, top content types)
+- **Bandwidth** (total bandwidth, encrypted and unencrypted traffic cached bandwidth, uncached bandwidth)
+- **Caching** (Cache hit rate, request caching rate over time)
+- **HTTP response status errors**
+- **Page views**
+- **Search Engine Bot Traffic**
+- **DNS** (DNS queries, response time, top hostnames, queries by type, stale vs. uncached queries)
 
 ![Dashboard displaying metrics for a site on a Cloudflare account](~/assets/images/fundamentals/datadog/dashboards/cloudflare-dashboard-datadog.png)

src/content/docs/analytics/analytics-integrations/datadog.mdx

@@ -1,5 +1,5 @@
 ---
-pcx_content_type: how-to
+pcx_content_type: tutorial
 title: Graylog
 sidebar:
   order: 102

src/content/docs/analytics/analytics-integrations/graylog.mdx

@@ -1,9 +1,8 @@
 ---
-pcx_content_type: how-to
+pcx_content_type: tutorial
 title: Looker
 sidebar:
   order: 102
-
 ---
 
 This tutorial explains how to analyze [Cloudflare Logs](https://www.cloudflare.com/products/cloudflare-logs/) using the [Cloudflare Log Analytics for Looker](https://marketplace.looker.com/marketplace/detail/cloudflare-log-analytics).
@@ -18,17 +17,15 @@ This tutorial uses Cloudflare Logpush to send logs to [Google Cloud Storage Buck
 
 Before sending your Cloudflare log data to Looker, make sure that you:
 
-* Have an existing Looker account
-* Have a Cloudflare Enterprise account with Cloudflare Logs enabled
-* Configure [Logpush](/logs/about/) or [Logpull](/logs/logpull/)
-* Load your data in a [database supported by Looker](https://looker.com/solutions/other-databases)
+- Have an existing Looker account
+- Have a Cloudflare Enterprise account with Cloudflare Logs enabled
+- Configure [Logpush](/logs/about/) or [Logpull](/logs/logpull/)
+- Load your data in a [database supported by Looker](https://looker.com/solutions/other-databases)
 
 :::note[Note]
 
-
 Cloudflare logs are HTTP/HTTPS request logs in JSON format and are gathered from our 200+ data centers globally. By default, timestamps are returned as UNIX nanosecond integers. We recommend using the RFC 3339 format for sending logs to Looker.
 
-
 :::
 
 ## Task 1 - Connect your Database to Looker
@@ -43,7 +40,7 @@ To create your new LookML project:
 
 1. Log in to your Looker account.
 
-2. In the menu bar, click **Develop** and make sure **Development Mode** is set to *ON*.
+2. In the menu bar, click **Develop** and make sure **Development Mode** is set to _ON_.
 
 3. Next, also under **Develop**, click **Manage LookML Projects**.
 
@@ -53,7 +50,7 @@ To create your new LookML project:
 
 6. For **Starting Point**, choose \*Clone Public Git Repository\*\*.\*\*\*
 
-7. Enter the *cloudflare\_block* URL for the public Git repository `git://github.com/llooker/cloudflare_block.git`.
+7. Enter the _cloudflare_block_ URL for the public Git repository `git://github.com/llooker/cloudflare_block.git`.
 
 8. Click **Create Project**. Looker will pull all of the repository files into a new LookML project.
 
@@ -66,7 +63,7 @@ To create your new LookML project:
 
 To update the connection name in the LookML files:
 
-1. In your LookML **cloudflare\_looker** model file, replace the **connection** name with yours, for example:
+1. In your LookML **cloudflare_looker** model file, replace the **connection** name with yours, for example:
    `connection: "bigquery_lpr"`.
 
 2. Check if any table names need to be updated to your database connection names as well. If you decide to rename the filenames for explore, model name, and view, make sure to update all mentions within the other files. Otherwise, you might encounter errors.
@@ -115,40 +112,40 @@ All dashboard have a set of filters that you can apply to the entire dashboard,
 
 ![List of the available filters from the Looker dashboard](~/assets/images/fundamentals/looker/screenshots/cloudflare-looker-dashboard-filters.png)
 
-The default time interval is set to 24 hours. Note that for correct calculations, by default, filters exclude Worker subrequests (**WorkerSubrequest** = *false*) and purge requests (**ClientRequestMethod** is not *PURGE*).
+The default time interval is set to 24 hours. Note that for correct calculations, by default, filters exclude Worker subrequests (**WorkerSubrequest** = _false_) and purge requests (**ClientRequestMethod** is not _PURGE_).
 
 Available Filters:
 
-* Date (EdgeStartTimestamp)
+- Date (EdgeStartTimestamp)
 
-* Device type
+- Device type
 
-* Country
+- Country
 
-* Client IP
+- Client IP
 
-* Hostname
+- Hostname
 
-* Request URI
+- Request URI
 
-* Origin Response Status
+- Origin Response Status
 
-* Edge response status
+- Edge response status
 
-* Origin IP
+- Origin IP
 
-* User Agent
+- User Agent
 
-* RayID
+- RayID
 
-* Worker Subrequest
+- Worker Subrequest
 
-* Client Request Method
+- Client Request Method
 
 With the following pre-set filter values in the Looker dashboards all workers subrequests and client request method PURGE are excluded from the calculations:
 
-* **WorkerSubrequest** set to value *False*
+- **WorkerSubrequest** set to value _False_
 
-* **ClientRequestMethod** does not equal to *PURGE*
+- **ClientRequestMethod** does not equal to _PURGE_
 
 You can always adjust your default filter values according to your needs.

src/content/docs/analytics/analytics-integrations/looker.mdx

@@ -1,9 +1,8 @@
 ---
-pcx_content_type: how-to
+pcx_content_type: tutorial
 title: New Relic
 sidebar:
   order: 103
-
 ---
 
 This tutorial explains how to analyze Cloudflare metrics using the [New Relic One Cloudflare Quickstart](https://newrelic.com/instant-observability/cloudflare/fc2bb0ac-6622-43c6-8c1f-6a4c26ab5434).
@@ -12,9 +11,9 @@ This tutorial explains how to analyze Cloudflare metrics using the [New Relic On
 
 Before sending your Cloudflare log data to New Relic, make sure that you:
 
-* Have a Cloudflare Enterprise account with Cloudflare Logs enabled.
-* Have a New Relic account.
-* Configure [Logpush to New Relic](/logs/get-started/enable-destinations/new-relic/).
+- Have a Cloudflare Enterprise account with Cloudflare Logs enabled.
+- Have a New Relic account.
+- Configure [Logpush to New Relic](/logs/get-started/enable-destinations/new-relic/).
 
 ## Task 1 - Install the Cloudflare Network Logs quickstart