diff --git a/src/content/docs/magic-network-monitoring/rules/dynamic-threshold.mdx b/src/content/docs/magic-network-monitoring/rules/dynamic-threshold.mdx index 28424f7b0de1463..8fae6d97ededd47 100644 --- a/src/content/docs/magic-network-monitoring/rules/dynamic-threshold.mdx +++ b/src/content/docs/magic-network-monitoring/rules/dynamic-threshold.mdx @@ -23,7 +23,7 @@ A dynamic threshold rule can only be configured via [Cloudflare's Magic Network | **Rule type** | zscore | | **Target** | Can be defined in either bits per second or packets per second. | | **Sensitivity** | Z-Score sensitivity has three values: low, medium, and high. | -| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more and see an example, view the [Auto-Advertisement section](/magic-network-monitoring/rules/rule-notifications/#rule-auto-advertisement-notifications). | +| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. Magic Network Monitoring supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](/magic-network-monitoring/rules/rule-notifications/#rule-auto-advertisement-notifications). | | **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and review an example, refer to the [Rule IP prefixes](/magic-network-monitoring/rules/#rule-ip-prefixes). | ## API documentation diff --git a/src/content/docs/magic-network-monitoring/rules/s-flow-ddos-attack.mdx b/src/content/docs/magic-network-monitoring/rules/s-flow-ddos-attack.mdx index 686dfe4fb9e8de7..b8e2bc9b8862cfe 100644 --- a/src/content/docs/magic-network-monitoring/rules/s-flow-ddos-attack.mdx +++ b/src/content/docs/magic-network-monitoring/rules/s-flow-ddos-attack.mdx @@ -23,8 +23,8 @@ Customers can export sFlow data of their network traffic to Cloudflare via Magic | :---- | :---- | | **Rule name** | Must be unique and cannot contain spaces. Supports characters `A-Z`, `a-z`, `0-9`, underscore (`_`), dash (`-`), period (`.`), and tilde (`~`). Maximum of 256 characters. | | **Rule type** | advanced_ddos | -| **Prefix Match** | The field `prefix_match` determines how IP matches are handled. | -| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more and see an example, view the [Auto-Advertisement section](/api/resources/magic_network_monitoring/subresources/rules/). | +| **Prefix Match** | The field `prefix_match` determines how IP matches are handled. | +| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule's dynamic threshold is triggered. To learn more refer to [Auto-Advertisement section](/magic-network-monitoring/rules/rule-notifications/#rule-auto-advertisement-notifications). | | **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. The maximum is 5,000 unique CIDR entries. To learn more and see an example, view the [Rule IP prefixes](/magic-network-monitoring/rules/#rule-ip-prefixes). | ## API documentation diff --git a/src/content/docs/magic-network-monitoring/rules/static-threshold.mdx b/src/content/docs/magic-network-monitoring/rules/static-threshold.mdx index b42ca48e0553ef5..13de33b81ed9978 100644 --- a/src/content/docs/magic-network-monitoring/rules/static-threshold.mdx +++ b/src/content/docs/magic-network-monitoring/rules/static-threshold.mdx @@ -18,7 +18,7 @@ Customers that send NetFlow and / or sFlow data to Cloudflare can configure stat | **Rule threshold type** | Can be defined in either bits per second or packets per second. | | **Rule threshold** | The number of bits per second or packets per second for the rule alert. When this value is exceeded for the rule duration, an alert notification is sent. Minimum of `1` and no maximum. | | **Rule duration** | The amount of time in minutes the rule threshold must exceed to send an alert notification. Choose from the following values: `1`, `5`, `10`, `15`, `20`, `30`, `45`, or `60` minutes. | -| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. To learn more and see an example, view the [Auto-Advertisement section](/magic-network-monitoring/rules/rule-notifications/#rule-auto-advertisement-notifications). | +| **Auto-advertisement** | If you are a [Magic Transit On Demand](/magic-transit/on-demand) customer, you can enable this feature to automatically enable Magic Transit if the rule alert is triggered. Magic Network Monitoring supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](/magic-network-monitoring/rules/rule-notifications/#rule-auto-advertisement-notifications). | | **Rule IP prefix** | The IP prefix associated with the rule for monitoring traffic volume. Must be a CIDR range such as `160.168.0.1/24`. Max is 5,000 unique CIDR entries. To learn more and see an example, view the [Rule IP prefixes](/magic-network-monitoring/rules/#rule-ip-prefixes) section. | ## API documentation