Skip to content

Commit cd42a4d

Browse files
vars
1 parent d5f4c65 commit cd42a4d

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

src/content/partials/networking-services/mnm/rules/dynamic-threshold.mdx

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,13 @@ params:
33
- productName
44
---
55

6-
76
A dynamic threshold rule (beta) will analyze a network's traffic patterns over time and automatically adjust the rule's DDoS threshold, in terms of bits or packets, based on traffic history. The total traffic across all IP prefixes and IP addresses in the rule is compared to the current value of the dynamic threshold. If the total traffic exceeds the dynamic threshold, then an alert is sent.
87

98
Dynamic thresholds are calculated using a statistical measure called [Z-score](https://en.wikipedia.org/wiki/Standard_score) (also referred to as standard score). Review [How the dynamic rule threshold is calculated](#how-the-dynamic-rule-threshold-is-calculated) to learn more.
109

1110
Customers that send NetFlow and/or sFlow data to Cloudflare can configure dynamic threshold rules.
1211

13-
A dynamic threshold rule can only be configured via [Cloudflare's Magic Network Monitoring Rules API](/api/resources/magic_network_monitoring/subresources/rules/). Today, customers are unable to configure dynamic threshold rules in the Cloudflare dashboard.
12+
A dynamic threshold rule can only be configured via [Cloudflare's {props.productName} Rules API](/api/resources/magic_network_monitoring/subresources/rules/). Today, customers are unable to configure dynamic threshold rules in the Cloudflare dashboard.
1413

1514
## Rule configuration fields
1615

@@ -20,7 +19,7 @@ A dynamic threshold rule can only be configured via [Cloudflare's Magic Network
2019
| **Rule type** | zscore |
2120
| **Target** | Can be defined in either bits per second or packets per second. |
2221
| **Sensitivity** | Z-Score sensitivity has three values: low, medium, and high. |
23-
| **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-auto-advertisement). |
22+
| **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. {props.productName} supports Magic Transit's supernet capability. To learn more refer to [Auto-Advertisement section](/magic-network-monitoring/rules/#rule-auto-advertisement). |
2423
| **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). |
2524

2625
## API documentation

0 commit comments

Comments
 (0)