Supported metrics for Microsoft.Web/hostingenvironments/multirolepools

The following table lists the metrics available for the Microsoft.Web/hostingenvironments/multirolepools 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 - Metrics export using data collection rules and Create diagnostic settings in Azure Monitor.

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

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

Active Requests
ActiveRequests Count Total (Sum) Instance PT1M Yes
Average Response Time (deprecated)

The average time taken for the front end to serve requests, in seconds.
AverageResponseTime Seconds Average Instance PT1M Yes
Data In

The average incoming bandwidth used across all front ends, in MiB.
BytesReceived Bytes Total (Sum) Instance PT1M Yes
Data Out

The average incoming bandwidth used across all front end, in MiB.
BytesSent Bytes Total (Sum) Instance PT1M Yes
CPU Percentage

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

The average number of both read and write requests that were queued on storage. A high disk queue length is an indication of an app that might be slowing down because of excessive disk I/O.
DiskQueueLength Count Average Instance PT1M Yes
Http 101

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

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

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

The count of requests resulting in HTTP 401 status code.
Http401 Count Total (Sum) Instance PT1M Yes
Http 403

The count of requests resulting in HTTP 403 status code.
Http403 Count Total (Sum) Instance PT1M Yes
Http 404

The count of requests resulting in HTTP 404 status code.
Http404 Count Total (Sum) Instance PT1M Yes
Http 406

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

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

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

The average number of HTTP requests that had to sit on the queue before being fulfilled. A high or increasing HTTP Queue length is a symptom of a plan under heavy load.
HttpQueueLength Count Average Instance PT1M Yes
Response Time

The time taken for the front end to serve requests, in seconds.
HttpResponseTime Seconds Average Instance PT1M Yes
Large App Service Plan Workers

Large App Service Plan Workers
LargeAppServicePlanInstances Count Average <none> PT1M Yes
Medium App Service Plan Workers

Medium App Service Plan Workers
MediumAppServicePlanInstances Count Average <none> PT1M Yes
Memory Percentage

The average memory used across all instances of front end.
MemoryPercentage Percent Average Instance PT1M Yes
Requests

The total number of requests regardless of their resulting HTTP status code.
Requests Count Total (Sum) Instance PT1M Yes
Small App Service Plan Workers

Small App Service Plan Workers
SmallAppServicePlanInstances Count Average <none> PT1M Yes
Total Front Ends

Total Front Ends
TotalFrontEnds Count Average <none> PT1M Yes

Next steps