Skip to content

Commit 8378120

Browse files
corrected names
1 parent c87725e commit 8378120

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

src/content/docs/magic-transit/network-health/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar:
77

88
import { DirectoryListing } from "~/components"
99

10-
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/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information about SLI and SLOs.
10+
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 [How Cloudflare calculates Magic Tunnel health alerts](/magic-transit/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information about SLI and SLOs.
1111

1212
There are two types of health checks available: endpoint and tunnel health checks.
1313

src/content/docs/magic-transit/network-health/magic-tunnel-health-check-calculation.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
pcx_content_type: navigation
3-
title: Magic Tunnel health check calculation
3+
title: How Cloudflare calculates Magic Tunnel health alerts
44
external_link: /magic-transit/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/
55
sidebar:
66
order: 5

src/content/docs/magic-wan/configuration/common-settings/sites.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To use a site, start by setting up your on-ramps. These can be [GRE or IPsec tun
2525
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.
2626
9. In **Magic WAN Health Check Alert** > **Notification name**, enter a name for the site's alert.
2727
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.
28-
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/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information.
28+
10. In **Alert sensitivity level** define the threshold for Magic Tunnel health alerts to be fired. Refer to [How Cloudflare calculates Magic Tunnel health alerts](/magic-wan/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information.
2929
11. Select **Complete setup** to finish setting up your site.
3030

3131
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.

src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The SLO threshold for Magic Tunnel health alerts is the percentage of successful
4444

4545
The time it takes to be alerted depends on the sensitivity level you configure for your SLO thresholds. Higher sensitivity levels will notify you faster when a tunnel's health degrades, but they may also trigger alerts for brief or minor disruptions. Lower sensitivity levels reduce the chance of false alarms but may delay notifications for less severe issues. While the underlying detection timing remains consistent across sensitivity levels, the speed of notification depends on how significantly the tunnel's health has dropped and the sensitivity you have chosen. Cloudflare recommends that you [test SLO thresholds](#test-slos) to decide which one better serves your use case.
4646

47-
Refer to <a href={props.magicTunnelHealthCheckCalculation}>Magic Tunnel health check calculation</a> for more information on this topic.
47+
Refer to <a href={props.magicTunnelHealthCheckCalculation}>How Cloudflare calculates Magic Tunnel health alerts</a> for more information on this topic.
4848

4949

5050
## Set up Magic Tunnel health alerts
@@ -61,7 +61,7 @@ Refer to <a href={props.magicTunnelHealthCheckCalculation}>Magic Tunnel health c
6161
5. Select **Alert by tunnel**.
6262
6. Enter a name and description for the notification.
6363
7. Add webhooks or an email address for the person who should receive the notification, and select **Next**.
64-
8. Select the **Alert Sensitivity Level** threshold from the dropdown menu. The threshold is predefined to _Medium (98.0)_. There are options available between _Minimum (95.0)_ and _Maximum (99.9)_. Refer to <a href={props.magicTunnelHealthCheckCalculation}>Magic Tunnel health check calculation</a> for more information on this topic.
64+
8. Select the **Alert Sensitivity Level** threshold from the dropdown menu. The threshold is predefined to _Medium (98.0)_. There are options available between _Minimum (95.0)_ and _Maximum (99.9)_. Refer to <a href={props.magicTunnelHealthCheckCalculation}>How Cloudflare calculates Magic Tunnel health alerts</a> for more information on this topic.
6565
9. From the **Alert interval** drop-down menu, set the minimum amount of time that must pass before a duplicate alert is sent to you. Options range from five minutes to seven days.
6666
10. Enable **Set as default alert for any new tunnels created in the future** if you want the alert sensitivity level you chose to be automatically applied to all new tunnels you create.
6767
11. Select **Next**.
@@ -75,7 +75,7 @@ Refer to <a href={props.magicTunnelHealthCheckCalculation}>Magic Tunnel health c
7575
5. Select **Alert by data center**.
7676
6. Enter a name and description for the notification.
7777
7. Add webhooks or an email address for the person who should receive the notification, and select **Next**.
78-
8. Select the **Alert Sensitivity Level** threshold from the dropdown menu. The threshold is predefined to _Medium (98.0)_. There are options available between _Minimum (95.0)_ and _Maximum (99.9)_. Refer to <a href={props.magicTunnelHealthCheckCalculation}>Magic Tunnel health check calculation</a> for more information on this topic.
78+
8. Select the **Alert Sensitivity Level** threshold from the dropdown menu. The threshold is predefined to _Medium (98.0)_. There are options available between _Minimum (95.0)_ and _Maximum (99.9)_. Refer to <a href={props.magicTunnelHealthCheckCalculation}>How Cloudflare calculates Magic Tunnel health alerts</a> for more information on this topic.
7979
9. From the **Alert interval** drop-down menu, set the minimum amount of time that must pass before a duplicate alert is sent to you. Options range from five minutes to seven days.
8080
10. Choose the data centers you want to receive alerts for, and select **Next**.
8181
11. Choose the tunnels you want to receive alerts for. You can search by specific tunnel names, or filter them by type (GRE, IPsec and CNI). Select **Next**.

0 commit comments

Comments
 (0)