We're excited to announce the public preview of peacetime telemetry for Azure DDoS Protection. The DDoS traffic metrics you rely on during an attack now show your traffic during normal operation too. You can learn what normal looks like, set alerts and test your monitoring well before you need them.
Why it matters
Azure DDoS Protection already monitors your traffic around the clock and mitigates attacks automatically, and that doesn't change. Peacetime telemetry adds visibility on top of that protection. Your teams get an everyday view of the traffic reaching your public IPs, in the same metrics they use during an attack, so they can understand that traffic and prepare their monitoring ahead of time.
What's new
Before this preview, the DDoS traffic metrics for a protected public IP address showed data only while a mitigation was active. Now they also show the traffic reaching the IP during normal operation: the total in Inbound packets DDoS, and a breakdown in Inbound TCP packets DDoS, Inbound SYN packets DDoS, Inbound UDP packets DDoS and Inbound other packets DDoS. "Other" covers all traffic that isn't TCP or UDP. At the same time, Under DDoS attack or not stays at 0, which means DDoS Protection doesn't report an attack.
These are the metrics you already know, and nothing is renamed. For the full list, see the monitoring data reference.
What you can do with it
- Learn your normal. Watch TCP, SYN, UDP and other traffic for each protected public IP over days and weeks, so you know your busy periods before an attack.
- Compare traffic with mitigation triggers. Chart observed packet rates next to the trigger metrics for the same IP to see how everyday traffic compares with the thresholds that start mitigation.
- Alert on traffic conditions. Create Azure Monitor metric alerts with thresholds that fit each workload. These alerts sit alongside your attack alerts; they don't replace them, and they don't change how mitigation starts.
- Test your monitoring with everyday traffic. Check that your charts, workbooks and alerts receive data without simulating an attack.
Availability and scope
- Both tiers. It works with DDoS Network Protection and DDoS IP Protection.
- The resources you already protect. It covers the same resources DDoS Protection supports today.
- Automatic. It's on for protected public IP addresses. You don't need to register.
- Nothing extra to set up. You can view the metrics in Azure Monitor without a Log Analytics workspace or diagnostic settings.
- No additional cost beyond your existing Azure DDoS Protection pricing. Standard Azure Monitor charges apply to alert rules.
- Public cloud, IPv4 and IPv6. During the preview, peacetime telemetry is available in the Azure public cloud, for IPv4 and IPv6 public IP addresses. It isn't available in sovereign clouds, such as Azure Government. The preview is subject to the Supplemental Terms of Use for Microsoft Azure Previews.
Get started
Before you begin, you need a public IP address protected by DDoS Network Protection or DDoS IP Protection, and permission to read its metrics.
- In the Azure portal, open the protected public IP address.
- Under Monitoring, select Metrics.
- Set the time granularity to 1 minute. Add Inbound TCP packets DDoS, Inbound UDP packets DDoS and Inbound SYN packets DDoS, each with Max aggregation. Packet metrics are already reported per second.
- Select New chart, and add Under DDoS attack or not with Max aggregation.
When the public IP receives normal traffic, the first chart shows that traffic and Under DDoS attack or not stays at 0.
Figure 1: The DDoS packet metrics for a protected public IP address during normal operation.
Figure 2: Normal traffic is visible while the attack status stays at 0.
To add a traffic alert, see Traffic-condition alerts during peacetime (preview). Base the threshold on the traffic you've seen, not on the attack-status value of 1.
Good to know
- Check alerts and automation that assume an attack. If a workbook, alert or script treats the presence of DDoS traffic data as a sign of an attack, update it to check Under DDoS attack or not instead.
- Protection doesn't change. Mitigation policies stay the same. Mitigation flow logs, reports and notifications are produced at the same times as before.
Learn more