Edit

Monitor Azure DDoS Protection

Azure Monitor collects and aggregates metrics and logs from your system to monitor availability, performance, and resilience, and notify you of issues affecting your system. You can use the Azure portal, PowerShell, Azure CLI, REST API, or client libraries to set up and view monitoring data.

Different metrics and logs are available for different resource types. This article describes the types of monitoring data you can collect for this service and ways to analyze that data.

Collect data with Azure Monitor

This table describes how you can collect data to monitor your service, and what you can do with the data once collected:

Data to collect Description How to collect and route the data Where to view the data Supported data
Metric data Metrics are numerical values that describe an aspect of a system at a particular point in time. Metrics can be aggregated using algorithms, compared to other metrics, and analyzed for trends over time. - Collected automatically at regular intervals.
- You can route some platform metrics to a Log Analytics workspace to query with other data. Check the DS export setting for each metric to see if you can use a diagnostic setting to route the metric data.
Metrics explorer Azure DDoS Protection metrics supported by Azure Monitor
Resource log data Logs are recorded system events with a timestamp. Logs can contain different types of data, and be structured or free-form text. You can route resource log data to Log Analytics workspaces for querying and analysis. Create a diagnostic setting to collect and route resource log data. Log Analytics Azure DDoS Protection resource log data supported by Azure Monitor
Activity log data The Azure Monitor activity log provides insight into subscription-level events. The activity log includes information like when a resource is modified or a virtual machine is started. - Collected automatically.
- Create a diagnostic setting to a Log Analytics workspace at no charge.
Activity log

For the list of all of the data supported by Azure Monitor, see:

Built in monitoring for Azure DDoS Protection

Azure DDoS Protection provides visibility into attack traffic and mitigation actions through metrics, reports, and flow logs. For eligible protected public IP addresses, peacetime telemetry also makes DDoS metrics available during normal operation, when mitigation isn't active.

Note

Upcoming changes to the diagnostic log schema (starting ~mid-August 2026) retire DDoSMitigationReports and add new fields to DDoSMitigationFlowLogs. For the full migration guidance, see DDoS Mitigation Reports.

Use Azure Monitor to view metrics, compare traffic patterns, and configure alerts. Peacetime metric availability doesn't change when mitigation flow logs, reports, or protection notifications are generated.

Peacetime telemetry availability (preview)

Peacetime telemetry extends the availability of the existing DDoS-specific metrics to normal operation for eligible protected public IP addresses. This scope includes incoming, forwarded, and dropped traffic, mitigation triggers, and attack status. Traffic metrics can contain data while Under DDoS attack or not reports 0. The mitigation-trigger metrics already support peacetime monitoring.

Peacetime telemetry supports the same resource types as Azure DDoS Protection. It is enabled automatically for supported resources protected by either DDoS Network Protection or DDoS IP Protection.

Important

Peacetime telemetry is in public preview. Use a protected public IP address that's eligible for the feature. Protection alone doesn't establish preview availability for every region, cloud, or IP version. See the Supplemental Terms of Use for Microsoft Azure Previews for applicable terms.

Peacetime telemetry uses the existing metric names and monitoring interfaces. It doesn't change the underlying protection or mitigation-policy behavior. For metric definitions and supported aggregations, see the monitoring data reference.

You can open the monitoring experience from a DDoS protection plan, virtual network, or public IP address. Confirm that the metric scope identifies the intended protected public IP address.

Logging can be further integrated with Microsoft Sentinel, Splunk (Azure Event Hubs), OMS Log Analytics, and Azure Storage for advanced analysis via the Azure Monitor Diagnostics interface.

For more information on metrics, see Monitoring Azure DDoS Protection for details on DDoS Protection monitoring logs.

View metrics from DDoS protection plan

  1. Sign in to the Azure portal and select your DDoS protection plan.

  2. On the Azure portal menu, select or search for and select DDoS protection plans then select your DDoS protection plan.

  3. Under Monitoring, select Metrics.

  4. Select Add metric then select Scope.

  5. In the Select a scope menu, select the Subscription that contains the public IP address you want to log.

  6. Select Public IP Address for Resource type then select the specific public IP address you want to log metrics for, and then select Apply.

  7. For Metric select Under DDoS attack or not.

  8. Select the Aggregation type as Max.

    Screenshot of creating DDoS protection metrics menu.

View metrics from virtual network

  1. Sign in to the Azure portal and browse to your virtual network that has DDoS protection enabled.

  2. Under Monitoring, select Metrics.

  3. Select Add metric then select Scope.

  4. In the Select a scope menu, select the Subscription that contains the public IP address you want to log.

  5. Select Public IP Address for Resource type then select the specific public IP address you want to log metrics for, and then select Apply.

  6. Under Metric select your chosen metric then under Aggregation select type as Max.

    Screenshot of DDoS diagnostic settings within Azure.

Note

To filter IP Addresses, select Add filter. Under Property, select Protected IP Address, and the operator should be set to =. Under Values, you see a dropdown of public IP addresses, associated with the virtual network, that are protected by Azure DDoS Protection.

View metrics from Public IP address

  1. Sign in to the Azure portal and browse to your public IP address.
  2. On the Azure portal menu, select or search for and select Public IP addresses then select your public IP address.
  3. Under Monitoring, select Metrics.
  4. Select Add metric then select Scope.
  5. In the Select a scope menu, select the Subscription that contains the public IP address you want to log.
  6. Select Public IP Address for Resource type then select the specific public IP address you want to log metrics for, and then select Apply.
  7. Under Metric select your chosen metric then under Aggregation select type as Max.

Note

When you change DDoS IP protection from enabled to disabled, telemetry for the public IP resource isn't available.

View DDoS mitigation policies

Azure DDoS Protection uses three automatically adjusted mitigation policies (TCP SYN, TCP, and UDP) for each public IP address of the resource being protected. This approach applies to any virtual network with DDoS protection enabled.

You can see the policy limits within your public IP address metrics by choosing the Inbound SYN packets to trigger DDoS mitigation, Inbound TCP packets to trigger DDoS mitigation, and Inbound UDP packets to trigger DDoS mitigation metrics. Make sure to set the aggregation type to Max.

Screenshot of viewing mitigation policies.

View peace time traffic telemetry

Use peacetime telemetry to understand normal TCP, UDP, SYN, and aggregate traffic patterns without waiting for an attack. You need an eligible protected public IP address and permission to read its metrics. A Log Analytics workspace or diagnostic setting isn't required to view platform metrics.

  1. In the Azure portal, open Public IP addresses and select the protected public IP address.
  2. Under Monitoring, select Metrics. Confirm that Scope identifies the intended public IP address.
  3. Select a recent time range, such as the last hour. Set Time granularity to 1 minute and apply the settings.
  4. Add Inbound TCP packets DDoS with Max aggregation.
  5. Add Inbound UDP packets DDoS and Inbound SYN packets DDoS, also with Max aggregation.
  6. Add a separate chart for Under DDoS attack or not, using the same public IP address, time range, granularity, and Max aggregation.
  7. Compare traffic and attack status. During normal operation, traffic metrics can contain data while the attack-status metric reports 0.

For aggregate traffic, use Inbound packets DDoS or Inbound bytes DDoS. Add the corresponding forwarded and dropped metrics when investigating filtering. Keep packet rates, byte rates, and attack status on separate charts.

For traffic that isn't TCP or UDP, use the existing Inbound other packets DDoS and Inbound other bytes DDoS metrics.

Note

DDoS traffic metrics already report bytes per second or packets per second. Don't divide these rates by 60. General public-IP metrics such as Packet Count, SYN Count, and Byte Count are separate measurements with different units and aggregations.

A reported attack-status value of 0 means no attack was reported for that measurement; 1 means an attack was reported. With Max, a displayed 1 means at least one reported value in that chart interval was 1, not necessarily that an attack is still active when you view the chart.

Missing data isn't the same as zero. If no data points appear, check protection and feature eligibility, public-IP scope, permissions, the selected time range, and reporting delay. Don't generate an attack to make metrics appear. For interpretation and timing guidance, see Interpret DDoS metrics.

Validate and test

Validate peacetime visibility with ordinary application traffic:

  1. Select an eligible protected test resource that's receiving ordinary application traffic.
  2. Follow the peacetime viewing procedure and allow for reporting delay.
  3. Confirm that relevant traffic metrics contain data and that Under DDoS attack or not reports 0 for the test period.
  4. Investigate missing values by checking feature eligibility, scope, permissions, the time range, and reporting delay.

This test validates metric visibility, not mitigation effectiveness or application health. Attack and mitigation validation are separate activities. Follow the approved DDoS simulation-testing process for those tests.

Use Azure Monitor tools to analyze the data

These Azure Monitor tools are available in the Azure portal to help you analyze monitoring data:

  • Some Azure services have a built-in monitoring dashboard in the Azure portal. These dashboards are called insights, and you can find them in the Insights section of Azure Monitor in the Azure portal.

  • Metrics explorer allows you to view and analyze metrics for Azure resources. For more information, see Analyze metrics with Azure Monitor metrics explorer.

  • Log Analytics allows you to query and analyze log data using the Kusto query language (KQL). For more information, see Get started with log queries in Azure Monitor.

  • The Azure portal has a user interface for viewing and basic searches of the activity log. To do more in-depth analysis, route the data to Azure Monitor logs and run more complex queries in Log Analytics.

  • Application Insights monitors the availability, performance, and usage of your web applications, so you can identify and diagnose errors without waiting for a user to report them.
    Application Insights includes connection points to various development tools and integrates with Visual Studio to support your DevOps processes. For more information, see Application monitoring for App Service.

Tools that allow more complex visualization include:

  • Dashboards that let you combine different kinds of data into a single pane in the Azure portal.
  • Workbooks, customizable reports that you can create in the Azure portal. Workbooks can include text, metrics, and log queries.
  • Grafana, an open platform tool that excels in operational dashboards. You can use Grafana to create dashboards that include data from multiple sources other than Azure Monitor.
  • Power BI, a business analytics service that provides interactive visualizations across various data sources. You can configure Power BI to automatically import log data from Azure Monitor to take advantage of these visualizations.

Export Azure Monitor data

You can export data out of Azure Monitor into other tools using:

To get started with the Azure Monitor REST API, see Azure monitoring REST API walkthrough.

Use Kusto queries to analyze log data

You can analyze Azure Monitor Log data using the Kusto query language (KQL). For more information, see Log queries in Azure Monitor.

Use Azure Monitor alerts to notify you of issues

Azure Monitor alerts allow you to identify and address issues in your system, and proactively notify you when specific conditions are found in your monitoring data before your customers notice them. You can alert on any metric or log data source in the Azure Monitor data platform. There are different types of Azure Monitor alerts depending on the services you're monitoring and the monitoring data you're collecting. See Choosing the right type of alert rule.

For more information about alerts in Azure DDoS Protection, see Configure Azure DDoS Protection metric alerts through portal and Configure Azure DDoS Protection diagnostic logging alerts.

For examples of common alerts for Azure resources, see Sample log alert queries.

Implementing alerts at scale

For some services, you can monitor at scale by applying the same metric alert rule to multiple resources of the same type that exist in the same Azure region. Azure Monitor Baseline Alerts (AMBA) provides a semi-automated method of implementing important platform metric alerts, dashboards, and guidelines at scale.