Azure Front Door monitoring data reference
This article contains all the monitoring reference information for this service.
See Monitor Azure Front Door for details on the data you can collect for Azure Front Door and how to use it.
Metrics
This section lists all the automatically collected platform metrics for this service. These metrics are also part of the global list of all platform metrics supported in Azure Monitor.
For information on metric retention, see Azure Monitor Metrics overview.
Important
Azure Front Door (classic) will be retired on March 31, 2027. To avoid any service disruption, it is important that you migrate your Azure Front Door (classic) profiles to Azure Front Door Standard or Premium tier by March 2027. For more information, see Azure Front Door (classic) retirement.
Supported metrics for Microsoft.Network/frontdoors
The following table lists the metrics available for the Microsoft.Network/frontdoors resource type.
- All columns might not be present in every table.
- Some columns might be beyond the viewing area of the page. Select Expand table to view all available columns.
Table headings
- Category - The metrics group or classification.
- Metric - The metric display name as it appears in the Azure portal.
- Name in REST API - The metric name as referred to in the REST API.
- Unit - Unit of measure.
- Aggregation - The default aggregation type. Valid values: Average (Avg), Minimum (Min), Maximum (Max), Total (Sum), Count.
- Dimensions - Dimensions available for the metric.
- Time Grains - Intervals at which the metric is sampled. For example,
PT1M
indicates that the metric is sampled every minute,PT30M
every 30 minutes,PT1H
every hour, and so on. - DS Export- Whether the metric is exportable to Azure Monitor Logs via diagnostic settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.
Category: Backend Health
Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
---|---|---|---|---|---|---|
Backend Health Percentage The percentage of successful health probes from the HTTP/S proxy to backends |
BackendHealthPercentage |
Percent | Average | Backend , BackendPool |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Category: Latency
Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
---|---|---|---|---|---|---|
Backend Request Latency The time calculated from when the request was sent by the HTTP/S proxy to the backend until the HTTP/S proxy received the last response byte from the backend |
BackendRequestLatency |
MilliSeconds | Average | Backend |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Total Latency The time calculated from when the client request was received by the HTTP/S proxy until the client acknowledged the last response byte from the HTTP/S proxy |
TotalLatency |
MilliSeconds | Average | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Category: Traffic
Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
---|---|---|---|---|---|---|
Backend Request Count The number of requests sent from the HTTP/S proxy to backends |
BackendRequestCount |
Count | Total (Sum) | HttpStatus , HttpStatusGroup , Backend |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Billable Response Size The number of billable bytes (minimum 2KB per request) sent as responses from HTTP/S proxy to clients. |
BillableResponseSize |
Bytes | Total (Sum) | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Request Count The number of client requests served by the HTTP/S proxy |
RequestCount |
Count | Total (Sum) | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Request Size The number of bytes sent as requests from clients to the HTTP/S proxy |
RequestSize |
Bytes | Total (Sum) | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Response Size The number of bytes sent as responses from HTTP/S proxy to clients |
ResponseSize |
Bytes | Total (Sum) | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Web Application Firewall Request Count The number of client requests processed by the Web Application Firewall |
WebApplicationFirewallRequestCount |
Count | Total (Sum) | PolicyName , RuleName , Action |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Supported metrics for Microsoft.Cdn/profiles
The following table lists the metrics available for the Microsoft.Cdn/profiles resource type.
- All columns might not be present in every table.
- Some columns might be beyond the viewing area of the page. Select Expand table to view all available columns.
Table headings
- Category - The metrics group or classification.
- Metric - The metric display name as it appears in the Azure portal.
- Name in REST API - The metric name as referred to in the REST API.
- Unit - Unit of measure.
- Aggregation - The default aggregation type. Valid values: Average (Avg), Minimum (Min), Maximum (Max), Total (Sum), Count.
- Dimensions - Dimensions available for the metric.
- Time Grains - Intervals at which the metric is sampled. For example,
PT1M
indicates that the metric is sampled every minute,PT30M
every 30 minutes,PT1H
every hour, and so on. - DS Export- Whether the metric is exportable to Azure Monitor Logs via diagnostic settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.
Category: Latency
Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
---|---|---|---|---|---|---|
Origin Latency The time calculated from when the request was sent by AFDX edge to the backend until AFDX received the last response byte from the backend. |
OriginLatency |
MilliSeconds | Average | Origin , Endpoint |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Total Latency The time calculated from when the client request was received by the HTTP/S proxy until the client acknowledged the last response byte from the HTTP/S proxy |
TotalLatency |
MilliSeconds | Average | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry , Endpoint |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Category: Origin Health
Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
---|---|---|---|---|---|---|
Origin Health Percentage The percentage of successful health probes from AFDX to backends. |
OriginHealthPercentage |
Percent | Average | Origin , OriginGroup |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Category: Request Status
Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
---|---|---|---|---|---|---|
Byte Hit Ratio This is the ratio of the total bytes served from the cache compared to the total response bytes |
ByteHitRatio |
Percent | Average | Endpoint |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Percentage of 4XX The percentage of all the client requests for which the response status code is 4XX |
Percentage4XX |
Percent | Average | Endpoint , ClientRegion , ClientCountry |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Percentage of 5XX The percentage of all the client requests for which the response status code is 5XX |
Percentage5XX |
Percent | Average | Endpoint , ClientRegion , ClientCountry |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Category: Traffic
Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
---|---|---|---|---|---|---|
Origin Request Count The number of requests sent from AFDX to origin. |
OriginRequestCount |
Count | Total (Sum) | HttpStatus , HttpStatusGroup , Origin , Endpoint |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Request Count The number of client requests served by the HTTP/S proxy |
RequestCount |
Count | Total (Sum) | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry , Endpoint |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Request Size The number of bytes sent as requests from clients to AFDX. |
RequestSize |
Bytes | Total (Sum) | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry , Endpoint |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Response Size The number of bytes sent as responses from HTTP/S proxy to clients |
ResponseSize |
Bytes | Total (Sum) | HttpStatus , HttpStatusGroup , ClientRegion , ClientCountry , Endpoint |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Web Application Firewall JS Challenge Request Count The number of JS challenge requests evaluated by the Web Application Firewall |
WebApplicationFirewallJsRequestCount |
Count | Total (Sum) | PolicyName , RuleName , Action |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Web Application Firewall Request Count The number of client requests processed by the Web Application Firewall |
WebApplicationFirewallRequestCount |
Count | Total (Sum) | PolicyName , RuleName , Action |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
Note
The metrics are recorded and stored free of charge for a limited period of time. For an extra cost, you can store for a longer period of time.
The following table provides more detailed descriptions for the metrics.
Metrics | Description |
---|---|
Byte Hit Ratio | The percentage of traffic that was served from the Azure Front Door cache, computed against the total egress traffic. The byte hit ratio is low if most of the traffic is forwarded to the origin rather than served from the cache. Byte Hit Ratio = (egress from edge - egress from origin)/egress from edge. Scenarios excluded from bytes hit ratio calculations:
|
Origin Health Percentage | The percentage of successful health probes sent from Azure Front Door to origins. |
Origin Latency | Azure Front Door calculates the time from sending the request to the origin to receiving the last response byte from the origin. WebSocket is excluded from the origin latency. |
Origin Request Count | The number of requests sent from Azure Front Door to origins. |
Percentage of 4XX | The percentage of all the client requests for which the response status code is 4XX. |
Percentage of 5XX | The percentage of all the client requests for which the response status code is 5XX. |
Request Count | The number of client requests served through Azure Front Door, including requests served entirely from the cache. |
Request Size | The number of bytes sent in requests from clients to Azure Front Door. |
Response Size | The number of bytes sent as responses from Front Door to clients. |
Total Latency | Azure Front Door receives the client request and sends the last response byte to the client. This value is the total time taken. For WebSocket, this metric refers to the time it takes to establish the WebSocket connection. |
Web Application Firewall Request Count | The number of requests processed by the Azure Front Door web application firewall. |
Note
If a request to the origin times out, the value of the Http Status dimension is 0.
Metric dimensions
For information about what metric dimensions are, see Multi-dimensional metrics.
This service has the following dimensions associated with its metrics.
- Action
- Backend
- BackendPool
- ClientCountry
- ClientRegion
- HttpStatus
- HttpStatusGroup
- PolicyName
- RuleName
- Action
- ClientCountry
- ClientRegion
- Endpoint
- HttpStatus
- HttpStatusGroup
- Origin
- OriginGroup
- PolicyName
- RuleName
Resource logs
This section lists the types of resource logs you can collect for this service. The section pulls from the list of all resource logs category types supported in Azure Monitor.
Supported resource logs for Microsoft.Network/frontdoors
Category | Category display name | Log table | Supports basic log plan | Supports ingestion-time transformation | Example queries | Costs to export |
---|---|---|---|---|---|---|
FrontdoorAccessLog |
Frontdoor Access Log | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
FrontdoorWebApplicationFirewallLog |
Frontdoor Web Application Firewall Log | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
Supported resource logs for Microsoft.Cdn/profiles
Category | Category display name | Log table | Supports basic log plan | Supports ingestion-time transformation | Example queries | Costs to export |
---|---|---|---|---|---|---|
AzureCdnAccessLog |
Azure Cdn Access Log | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
FrontDoorAccessLog |
FrontDoor Access Log | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | Yes |
FrontDoorHealthProbeLog |
FrontDoor Health Probe Log | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | Yes |
FrontDoorWebApplicationFirewallLog |
FrontDoor WebApplicationFirewall Log | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | Yes |
Supported resource logs for Microsoft.Cdn/profiles/endpoints
Category | Category display name | Log table | Supports basic log plan | Supports ingestion-time transformation | Example queries | Costs to export |
---|---|---|---|---|---|---|
CoreAnalytics |
Gets the metrics of the endpoint, e.g., bandwidth, egress, etc. | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
Azure Monitor Logs tables
This section lists the Azure Monitor Logs tables relevant to this service, which are available for query by Log Analytics using Kusto queries. The tables contain resource log data and possibly more depending on what is collected and routed to them.
Azure Front Door Microsoft.Network/frontdoors
Azure Front Door Microsoft.Cdn/profiles
Activity log
The linked table lists the operations that can be recorded in the activity log for this service. These operations are a subset of all the possible resource provider operations in the activity log.
For more information on the schema of activity log entries, see Activity Log schema.
Related content
- See Monitor Azure Front Door for a description of monitoring Azure Front Door.
- See Monitor Azure resources with Azure Monitor for details on monitoring Azure resources.