[MWAN/MT] Tunnel HCs (#22262)

marciocloudflare · daisyfaithauma · commit 99f57308ef52 · 2025-05-08T11:48:00.000+03:00
* added th page

* changed page weights

* moved health pages

* added intro

* refined text

* added new steps

* added alerts by tunnel

* renamed files

* added redirects

* changed name to network health

* corrected redirects

* added info on sli slo

* changed page name

* added link page

* removed extra space

* changed page name

* refined text

* changed page weights

* added beta and changed page link name

* changed page names

* changed var name

* changed var name

* refined alert levels

* removed rec slos

* refined text

* corrected links

* refined text

* corrected var

* refined text

* corrected link
diff --git a/public/__redirects b/public/__redirects
@@ -850,6 +850,10 @@
 /magic-transit/reference/ /magic-transit/reference/anti-replay-protection/ 301
 /magic-transit/how-to/configure-static-routes/ /magic-transit/how-to/configure-routes/ 301
 /magic-transit/how-to/bgp-peering/ /magic-transit/how-to/configure-routes/ 301
+/magic-transit/how-to/run-endpoint-health-checks/ /magic-transit/network-health/run-endpoint-health-checks/ 301
+/magic-transit/how-to/check-tunnel-health-dashboard/ /magic-transit/network-health/check-tunnel-health-dashboard/ 301
+/magic-transit/how-to/configure-magic-tunnel-alerts/ /magic-transit/network-health/configure-magic-tunnel-alerts/ 301
+/magic-transit/how-to/tunnel-health-checks/ /magic-transit/network-health/update-tunnel-health-checks/ 301
 
 # magic-wan
 /magic-wan/tutorials/ipsec/ /magic-wan/reference/tunnels/#ipsec-tunnels 301
diff --git a/src/content/docs/magic-transit/alerts.mdx b/src/content/docs/magic-transit/alerts.mdx
@@ -2,7 +2,7 @@
 title: Alerts
 pcx_content_type: reference
 sidebar:
-  order: 11
+  order: 13
 
 ---
 
diff --git a/src/content/docs/magic-transit/analytics/index.mdx b/src/content/docs/magic-transit/analytics/index.mdx
@@ -2,7 +2,7 @@
 title: Analytics
 pcx_content_type: how-to
 sidebar:
-  order: 7
+  order: 8
 head: []
 description: Use Magic Transit's different analytic options for an overview of
   the performance of your sites, or to troubleshoot potential issues.
diff --git a/src/content/docs/magic-transit/changelog.mdx b/src/content/docs/magic-transit/changelog.mdx
@@ -2,7 +2,7 @@
 pcx_content_type: changelog
 title: Changelog
 sidebar:
-  order: 14
+  order: 16
 head: []
 description: Review recent changes to Magic Transit.
 ---
diff --git a/src/content/docs/magic-transit/cloudflare-ips.mdx b/src/content/docs/magic-transit/cloudflare-ips.mdx
@@ -2,7 +2,7 @@
 title: Cloudflare IPs
 pcx_content_type: concept
 sidebar:
-  order: 8
+  order: 10
 
 ---
 
@@ -14,8 +14,8 @@ To protect your network using a Cloudflare IP address, contact your account mana
 
 - [Create a tunnel](/magic-transit/how-to/configure-tunnels/).
 - [Set up static routes](/magic-transit/how-to/configure-routes/#configure-static-routes) or [BGP peering](/magic-transit/how-to/configure-routes/#configure-bgp-routes).
-- [Configure health checks](/magic-transit/how-to/run-endpoint-health-checks).
-- Confirm [tunnel](/magic-transit/how-to/tunnel-health-checks/) and endpoint health checks were properly configured.
+- [Configure health checks](/magic-transit/network-health/run-endpoint-health-checks/).
+- Confirm [tunnel](/magic-transit/network-health/update-tunnel-health-checks/) and endpoint health checks were properly configured.
 - Update your infrastructure at your own pace to use the allocated Cloudflare IPs.
 
 When you use a Cloudflare-owned IP space, you do not need a <GlossaryTooltip term="letter of agency" link="/magic-transit/get-started/#draft-letter-of-agency">Letter of Agency (LOA)</GlossaryTooltip>. You can skip this step from the Prerequisites page.
diff --git a/src/content/docs/magic-transit/ddos.mdx b/src/content/docs/magic-transit/ddos.mdx
@@ -2,7 +2,7 @@
 title: DDoS protection
 pcx_content_type: concept
 sidebar:
-  order: 6
+  order: 7
 head:
   - tag: title
     content: Cloudflare DDoS protection
diff --git a/src/content/docs/magic-transit/how-to/configure-tunnels.mdx b/src/content/docs/magic-transit/how-to/configure-tunnels.mdx
@@ -21,11 +21,11 @@ import { GlossaryTooltip, Render } from "~/components";
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
 		productPathDash: "Magic Transit > Configuration",
-		updateHCFrequencyPage: "/magic-transit/how-to/tunnel-health-checks/",
+		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		biVsUniHealthCheck: "unidirectional",
-		tunnelHealthDash: "/magic-transit/how-to/check-tunnel-health-dashboard/",
+		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
 		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional"
 	}} />
 
diff --git a/src/content/docs/magic-transit/magic-network-monitoring.mdx b/src/content/docs/magic-transit/magic-network-monitoring.mdx
@@ -2,7 +2,7 @@
 title: Magic Network Monitoring
 pcx_content_type: concept
 sidebar:
-  order: 7
+  order: 9
 
 ---
 
diff --git a/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx b/src/content/docs/magic-transit/network-health/check-tunnel-health-dashboard.mdx
@@ -1,6 +1,8 @@
 ---
 pcx_content_type: how-to
 title: Check tunnel health in the dashboard
+sidebar:
+  order: 2
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/magic-transit/network-health/configure-magic-tunnel-alerts.mdx b/src/content/docs/magic-transit/network-health/configure-magic-tunnel-alerts.mdx
@@ -3,6 +3,8 @@ pcx_content_type: how-to
 title: Configure Magic Tunnel health alerts
 head: []
 description: Use the API to set up and configure Magic Tunnel health alerts
+sidebar:
+  order: 4
 ---
 
 import { Render } from "~/components";
@@ -13,7 +15,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		backgroundInfoPath: "/magic-transit/reference/magic-tunnels/",
+		magicTunnelHealthCheckCalculation: "/magic-transit/reference/magic-tunnels/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}
diff --git a/src/content/docs/magic-transit/network-health/index.mdx b/src/content/docs/magic-transit/network-health/index.mdx
@@ -0,0 +1,30 @@
+---
+pcx_content_type: navigation
+title: Network health
+sidebar:
+  order: 6
+---
+
+import { DirectoryListing } from "~/components"
+
+Magic Transit uses health checks probes to determine the status of tunnels. This information is used to steer traffic through the best available route, and to warn you about potential issues with a tunnel. Service-level indicators (SLI) and service-level objectives (SLOs) combine to determine when Cloudflare sends you tunnel health alerts. Refer to [Magic Tunnel health check calculation](/magic-transit/reference/magic-tunnels/) for more information about SLI and SLOs.
+
+There are two types of health checks available: endpoint and tunnel health checks.
+
+ - Endpoint health checks evaluate connectivity from Cloudflare distributed data centers to your origin network. Designed to provide a broad picture of Internet health, endpoint probes flow over available tunnels and do not inform tunnel selection or steering logic.
+
+	Cloudflare global network servers issue endpoint health checks outside of customer network namespaces and typically target endpoints beyond the tunnel-terminating border router.
+
+	During onboarding, you specify IP addresses to configure endpoint health checks.
+
+- Tunnel health checks monitor the status of the tunnels that route traffic from Cloudflare to your origin network. Magic Transit relies on health checks to steer traffic to the best available routes.
+
+	During onboarding, you specify the tunnel endpoints or tunnel health check targets the tunnel probes originating from Cloudflare's global network will target.
+
+	Tunnel health check results are exposed via API. These results are aggregated from individual health check results done on Cloudflare servers.
+
+Refer to [Tunnel health checks](/magic-transit/reference/tunnel-health-checks/) for a deep dive on the different type of health checks, what they do and how they work.
+
+Refer to the pages below for details on how to use the various network health checks available.
+
+<DirectoryListing />
diff --git a/src/content/docs/magic-transit/network-health/magic-tunnel-health-check-calculation.mdx b/src/content/docs/magic-transit/network-health/magic-tunnel-health-check-calculation.mdx
@@ -0,0 +1,7 @@
+---
+pcx_content_type: navigation
+title: Magic Tunnel health check calculation
+external_link: /magic-transit/reference/magic-tunnels/
+sidebar:
+  order: 5
+---
diff --git a/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx b/src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx
@@ -2,7 +2,7 @@
 pcx_content_type: how-to
 title: Run endpoint health checks
 sidebar:
-  order: 6
+  order: 1
 
 ---
 
diff --git a/src/content/docs/magic-transit/network-health/update-tunnel-health-checks.mdx b/src/content/docs/magic-transit/network-health/update-tunnel-health-checks.mdx
@@ -1,6 +1,8 @@
 ---
 pcx_content_type: how-to
 title: Update tunnel health checks frequency
+sidebar:
+  order: 3
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/docs/magic-transit/network-interconnect.mdx b/src/content/docs/magic-transit/network-interconnect.mdx
@@ -2,7 +2,7 @@
 title: Network Interconnect (CNI)
 pcx_content_type: concept
 sidebar:
-  order: 10
+  order: 12
 head:
   - tag: title
     content: Network Interconnect and Magic Transit
diff --git a/src/content/docs/magic-transit/on-demand.mdx b/src/content/docs/magic-transit/on-demand.mdx
@@ -2,7 +2,7 @@
 title: Magic Transit on-demand
 pcx_content_type: concept
 sidebar:
-  order: 9
+  order: 11
 head:
   - tag: title
     content: Magic Transit on-demand
diff --git a/src/content/docs/magic-transit/partners/index.mdx b/src/content/docs/magic-transit/partners/index.mdx
@@ -2,7 +2,7 @@
 title: Partners
 pcx_content_type: navigation
 sidebar:
-  order: 12
+  order: 14
   group:
     hideIndex: true
 
diff --git a/src/content/docs/magic-transit/reference/index.mdx b/src/content/docs/magic-transit/reference/index.mdx
@@ -2,7 +2,7 @@
 title: Reference
 pcx_content_type: navigation
 sidebar:
-  order: 13
+  order: 15
   group:
     hideIndex: true
 
diff --git a/src/content/docs/magic-transit/reference/magic-tunnels.mdx b/src/content/docs/magic-transit/reference/magic-tunnels.mdx
@@ -1,6 +1,6 @@
 ---
 pcx_content_type: concept
-title: Magic Tunnels background information
+title: Magic Tunnel health check calculation
 
 ---
 
diff --git a/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx b/src/content/docs/magic-transit/reference/tunnel-health-checks.mdx
@@ -13,7 +13,7 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		addTunnels: "/magic-transit/how-to/configure-tunnels/#add-tunnels",
-		changeHealthCheckRate: "/magic-transit/how-to/tunnel-health-checks/",
+		changeHealthCheckRate: "/magic-transit/network-health/update-tunnel-health-checks/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Magic Transit",
 		staticRoutes: "/magic-transit/how-to/configure-routes/",
diff --git a/src/content/docs/magic-wan/configuration/common-settings/configure-magic-tunnel-alerts.mdx b/src/content/docs/magic-wan/configuration/common-settings/configure-magic-tunnel-alerts.mdx
@@ -13,7 +13,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic WAN",
 		productName: "Magic WAN",
-		backgroundInfoPath: "/magic-wan/reference/magic-tunnels/",
+		magicTunnelHealthCheckCalculation: "/magic-wan/reference/magic-tunnels/",
 		networkAnalyticsPath: "/magic-wan/analytics/network-analytics/",
 		healthChecks: "/magic-wan/reference/tunnel-health-checks/",
 	}}
diff --git a/src/content/docs/magic-wan/configuration/common-settings/sites.mdx b/src/content/docs/magic-wan/configuration/common-settings/sites.mdx
@@ -25,7 +25,7 @@ To use a site, start by setting up your on-ramps. These can be [GRE or IPsec tun
 8. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
 9. In **Magic WAN Health Check Alert** > **Notification name**, enter a name for the site's alert.
 9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
-10. In **Alert sensitivity level** define the threshold for Magic Tunnel health alerts to be fired. Available options are _Low_, _Medium_, and _High_. Refer to [Magic Tunnels background information](/magic-wan/reference/magic-tunnels/) for more information.
+10. In **Alert sensitivity level** define the threshold for Magic Tunnel health alerts to be fired. Refer to [Magic Tunnel health check calculation](/magic-wan/reference/magic-tunnels/) for more information.
 11. Select **Complete setup** to finish setting up your site.
 
 Your site is now set up. If you have other sites you need to set up, repeat the steps above. If you did not set up alerts, we strongly recommend that you do it. Otherwise you will not be notified when there is a problem with one of your on-ramps.
diff --git a/src/content/docs/magic-wan/reference/magic-tunnels.mdx b/src/content/docs/magic-wan/reference/magic-tunnels.mdx
@@ -1,6 +1,6 @@
 ---
 pcx_content_type: concept
-title: Magic Tunnels background information
+title: Magic Tunnel health check calculation
 
 ---
 
diff --git a/src/content/notifications/index.yaml b/src/content/notifications/index.yaml
@@ -36,7 +36,7 @@ entries:
     additional_information: |-
       After an alert is created on the dashboard, it may take up to 30 minutes before sufficient data is available to begin detecting traffic anomalies. Verified bot traffic is excluded from both basic and advanced bot alerts.
 
-      Alerts with grouping could cause potential noise if you set them up for a high-traffic zone. Grouping alerts function as if you set up separate policies with a filter for each value. Alerts may trigger multiple values in the same group as long as the traffic for each value reaches the threshold of 200. 
+      Alerts with grouping could cause potential noise if you set them up for a high-traffic zone. Grouping alerts function as if you set up separate policies with a filter for each value. Alerts may trigger multiple values in the same group as long as the traffic for each value reaches the threshold of 200.
 
   - name: Brand Protection Alerts
     audience: Customers who want a summary of activity related to [Brand Protection](/security-center/brand-protection/).
@@ -238,7 +238,7 @@ entries:
     audience: Magic Transit and Magic WAN customers who wish to receive alerts when the percentage of tunnel states meeting the selected service-level objective (SLO) drops below the defined threshold for a Magic Tunnel.
     availability: Purchase of Magic Transit and Magic WAN.
     associatedProducts: Magic Transit
-    nextSteps: Refer to the [Magic Transit tunnel health](/magic-transit/how-to/check-tunnel-health-dashboard/) or [Magic WAN tunnel health](/magic-wan/configuration/common-settings/check-tunnel-health-dashboard/) for more information on what the issue might be.
+    nextSteps: Refer to the [Magic Transit tunnel health](/magic-transit/network-health/check-tunnel-health-dashboard/) or [Magic WAN tunnel health](/magic-wan/configuration/common-settings/check-tunnel-health-dashboard/) for more information on what the issue might be.
     otherFilters: |-
       * Notification Name: A custom name for the notification.
       * Description (optional): A custom description for the notification.
diff --git a/src/content/partials/networking-services/routing/configure-tunnels.mdx b/src/content/partials/networking-services/routing/configure-tunnels.mdx
@@ -83,7 +83,7 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb
 11. _(Optional)_ **Tunnel health checks** are enabled by default. If you disable Tunnel health checks, your tunnels will appear 100% down in your <a href={props.tunnelHealthDash}>tunnel health dashboard</a> even when working. Cloudflare will keep sending traffic through the tunnel, without the means to detect if the tunnel goes down. You will have to set up your own system to detect down tunnels, as Cloudflare will not be able to warn you about down tunnels. Refer to <a href={props.tunnelHealthChecksPage}>Tunnel health checks</a> for more information.
 12. _(Optional)_ If you keep **Tunnel health checks** enabled, choose the <a href={props.updateHCFrequencyPage}>**Health check rate**</a> for your tunnel. Available options are _Low_, _Medium_, and _High_.
 13. The **Health check type** defaults to _Reply_ and to creating an ICMP reply. If your firewall drops this type of packet for assuming it is a type of attack, change this option to _Request_ which will create an ICMP request. Refer to <a href={props.tunnelHealthChecksPage}>Tunnel health checks</a> for more information.
-14. The **Health check direction** defaults to **{props.BiVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details.
+14. The **Health check direction** defaults to **{props.biVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details.
 15. _(Optional)_ **Health check target** is the customer end of the tunnel. This field is only visible when the **Health check direction** is set to _Unidirectional_.
 16. _(Optional)_ We recommend you test your tunnel before officially adding it. To test the tunnel, select **Test tunnels**.
 17. To add multiple tunnels, select **Add GRE tunnel** for each new tunnel.
@@ -101,7 +101,7 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb
 10. _(Optional)_ **Tunnel health checks** are enabled by default. If you disable Tunnel health checks, your tunnels will appear 100% down in your <a href={props.tunnelHealthDash}>tunnel health dashboard</a> even when working. Cloudflare will keep sending traffic through the tunnel, without the means to detect if the tunnel goes down. You will have to set up your own system to detect down tunnels, as Cloudflare will not be able to warn you about down tunnels. Refer to <a href={props.tunnelHealthChecksPage}>Tunnel health checks</a> for more information.
 11. _(Optional)_ If you keep **Tunnel health checks** enabled, choose the <a href={props.updateHCFrequencyPage}>**Health check rate**</a> for your tunnel. Available options are _Low_, _Medium_ and _High_.
 12. _(Optional)_ The **Health check type** defaults to _Reply_ and to creating an ICMP reply. If your firewall drops this type of packet for assuming it is a type of attack, change this option to _Request_ which will create an ICMP request. Refer to <a href={props.tunnelHealthChecksPage}>Tunnel health checks</a> for more information.
-13. _(Optional)_ The **Health check direction** defaults to **{props.BiVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details.
+13. _(Optional)_ The **Health check direction** defaults to **{props.biVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details.
 14. _(Optional)_ **Health check target** is the customer end of the tunnel. This field is only visible when the **Health check direction** is set to _Unidirectional_.
 
     :::note
diff --git a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx
