Supported metrics for Microsoft.Web/hostingEnvironments

  • Article

The following table lists the metrics available for the Microsoft.Web/hostingEnvironments resource type.

Table headings

Metric - The metric display name as it appears in the Azure portal.
Name in Rest API - Metric name as referred to in the REST API.
Unit - Unit of measure.
Aggregation - The default aggregation type. Valid values: Average, Minimum, Maximum, Total, 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.

For information on metric retention, see Azure Monitor Metrics overview.

For a list of supported logs, see Supported log categories - Microsoft.Web/hostingEnvironments

Metric Name in REST API Unit Aggregation Dimensions Time Grains DS Export
Active Requests (deprecated)

Number of requests being actively handled by the App Service Environment at any given time		 ActiveRequests Count Total (Sum) Instance PT1M Yes
Average Response Time (deprecated)

Average time taken for the ASE to serve requests		 AverageResponseTime Seconds Average Instance PT1M Yes
Data In

Incoming bandwidth used across all front end instances		 BytesReceived Bytes Total (Sum) Instance PT1M Yes
Data Out

Outgoing bandwidth used across all front end instances		 BytesSent Bytes Total (Sum) Instance PT1M Yes
CPU Percentage

CPU used across all front end instances		 CpuPercentage Percent Average Instance PT1M Yes
Disk Queue Length

Number of both read and write requests that were queued on storage		 DiskQueueLength Count Average Instance PT1M Yes
Http 101

Number of requests resulting in an HTTP 101 status code		 Http101 Count Total (Sum) Instance PT1M Yes
Http 2xx

Number of requests resulting in an HTTP status code >= 200 but < 300		 Http2xx Count Total (Sum) Instance PT1M Yes
Http 3xx

Number of requests resulting in an HTTP status code >= 300 but < 400		 Http3xx Count Total (Sum) Instance PT1M Yes
Http 401

Number of requests resulting in an HTTP 401 status code		 Http401 Count Total (Sum) Instance PT1M Yes
Http 403

Number of requests resulting in an HTTP 403 status code		 Http403 Count Total (Sum) Instance PT1M Yes
Http 404

Number of requests resulting in an HTTP 404 status code		 Http404 Count Total (Sum) Instance PT1M Yes
Http 406

Number of requests resulting in an HTTP 406 status code		 Http406 Count Total (Sum) Instance PT1M Yes
Http 4xx

Number of requests resulting in an HTTP status code >= 400 but < 500		 Http4xx Count Total (Sum) Instance PT1M Yes
Http Server Errors

Number of requests resulting in an HTTP status code >= 500 but < 600		 Http5xx Count Total (Sum) Instance PT1M Yes
Http Queue Length

Number of HTTP requests that had to sit on the queue before being fulfilled		 HttpQueueLength Count Average Instance PT1M Yes
Response Time

Time taken for the ASE to serve requests		 HttpResponseTime Seconds Average Instance PT1M Yes
Large App Service Plan Workers

Number of large App Service Plan worker instances		 LargeAppServicePlanInstances Count Average <none> PT1M Yes
Medium App Service Plan Workers

Number of medium App Service Plan worker instances		 MediumAppServicePlanInstances Count Average <none> PT1M Yes
Memory Percentage

Memory used across all front end instances		 MemoryPercentage Percent Average Instance PT1M Yes
Requests

Number of web requests served		 Requests Count Total (Sum) Instance PT1M Yes
Small App Service Plan Workers

Number of small App Service Plan worker instances		 SmallAppServicePlanInstances Count Average <none> PT1M Yes
Total Front Ends

Number of front end instances		 TotalFrontEnds Count Average <none> PT1M Yes

Next steps