Skip to content

Commit 787e208

Browse files
committed
included peace time traffic telemetry section.
1 parent ca2f369 commit 787e208

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

articles/ddos-protection/telemetry.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: ddos-protection
55
author: AbdullahBell
66
ms.service: ddos-protection
77
ms.topic: tutorial
8-
ms.date: 11/06/2023
8+
ms.date: 05/09/2024
99
ms.author: abell
1010
---
1111
# Tutorial: View and configure Azure DDoS protection telemetry
@@ -72,6 +72,7 @@ For more information on metrics, see [Monitoring Azure DDoS Protection](monitor-
7272

7373
>[!NOTE]
7474
>When changing DDoS IP protection from **enabled** to **disabled**, telemetry for the public IP resource will not be available.
75+
7576
## View DDoS mitigation policies
7677

7778
Azure DDoS Protection applies three auto-tuned mitigation policies (TCP SYN, TCP & UDP) for each public IP address of the protected resource, in the virtual network that has DDoS protection enabled. You can view the policy thresholds by selecting the **Inbound TCP packets to trigger DDoS mitigation** and **Inbound UDP packets to trigger DDoS mitigation** metrics with **aggregation** type as 'Max', as shown in the following picture:
@@ -81,6 +82,23 @@ Azure DDoS Protection applies three auto-tuned mitigation policies (TCP SYN, TCP
8182

8283
To simulate a DDoS attack to validate DDoS protection telemetry, see [Validate DDoS detection](test-through-simulations.md).
8384

85+
86+
## View peace time traffic telemetry
87+
88+
It's important to keep an eye on the metrics for TCP SYN, UDP, and TCP detection triggers. These metrics help you know when DDoS protection starts. Make sure these triggers reflect the normal traffic levels when there's no attack.
89+
90+
You can make a chart for the public IP address resource. In this chart, include the Packet Count (number of packets), Byte Count (amount of data), and Syn Count (number of synchronization packets) metrics. This will show you the sum of traffic.
91+
92+
93+
1. Sign in to the [Azure portal](https://portal.azure.com/) and browse to your public IP address.
94+
1. On the Azure portal menu, select or search for and select **Public IP addresses** then select your public IP address.
95+
1. Under **Monitoring**, select **Metrics**.
96+
1. Select your metrics and scope as described in the previous sections.
97+
1. Create a chart with the metrics you want to monitor. In this example we chose *Byte Count*, *Packet Count*, and *Syn Count* set to *Sum*.
98+
99+
>[!NOTE]
100+
> To make a fair comparison, you need to convert the data to packets-per-second. You can do this by dividing the number you see by 60, as the data represents the number of packets, bytes, or SYN packets collected over 60 seconds. For example, if you have 91,000 packets collected over 60 seconds, divide 91,000 by 60 to get approximately 1,500 packets-per-second (pps).
101+
84102
## Next steps
85103

86104
In this tutorial, you learned how to:

0 commit comments

Comments
 (0)