Azure App Service Alert metrics

MetricDescription
Response TimeThe time taken for the app to serve requests, in seconds.
Average Response Time (deprecated)The average time taken for the app to serve requests, in seconds.
Average memory working setThe average amount of memory used by the app, in megabytes (MiB).
ConnectionsThe number of bound sockets existing in the sandbox (w3wp.exe and its child processes). A bound socket is created by calling bind()/connect() APIs and remains until said socket is closed with CloseHandle()/closesocket().
CPU TimeThe amount of CPU consumed by the app, in seconds. For more information about this metric, see CPU time vs CPU percentage.
Current AssembliesThe current number of Assemblies loaded across all AppDomains in this application.
Data InThe amount of incoming bandwidth consumed by the app, in MiB.
Data OutThe amount of outgoing bandwidth consumed by the app, in MiB.
File System UsageThe amount of usage in bytes by storage share.
Gen 0 Garbage CollectionsThe number of times the generation 0 objects are garbage collected since the start of the app process. Higher generation GCs include all lower generation GCs.
Gen 1 Garbage CollectionsThe number of times the generation 1 objects are garbage collected since the start of the app process. Higher generation GCs include all lower generation GCs.
Gen 2 Garbage CollectionsThe number of times the generation 2 objects are garbage collected since the start of the app process.
Handle CountThe total number of handles currently open by the app process.
Health Check StatusThe average health status across the application’s instances in the App Service Plan.
Http 2xxThe count of requests resulting in an HTTP status code ≥ 200 but < 300.
Http 3xxThe count of requests resulting in an HTTP status code ≥ 300 but < 400.
Http 401The count of requests resulting in HTTP 401 status code.
Http 403The count of requests resulting in HTTP 403 status code.
Http 404The count of requests resulting in HTTP 404 status code.
Http 406The count of requests resulting in HTTP 406 status code.
Http 4xxThe count of requests resulting in an HTTP status code ≥ 400 but < 500.
Http Server ErrorsThe count of requests resulting in an HTTP status code ≥ 500 but < 600.
IO Other Bytes Per SecondThe rate at which the app process is issuing bytes to I/O operations that don’t involve data, such as control operations.
IO Other Operations Per SecondThe rate at which the app process is issuing I/O operations that aren’t read or write operations.
IO Read Bytes Per SecondThe rate at which the app process is reading bytes from I/O operations.
IO Read Operations Per SecondThe rate at which the app process is issuing read I/O operations.
IO Write Bytes Per SecondThe rate at which the app process is writing bytes to I/O operations.
IO Write Operations Per SecondThe rate at which the app process is issuing write I/O operations.
Memory working setThe current amount of memory used by the app, in MiB.
Private BytesPrivate Bytes is the current size, in bytes, of memory that the app process has allocated that can’t be shared with other processes.
RequestsThe total number of requests regardless of their resulting HTTP status code.
Requests In Application QueueThe number of requests in the application request queue.
Thread CountThe number of threads currently active in the app process.
Total App DomainsThe current number of AppDomains loaded in this application.
Total App Domains UnloadedThe total number of AppDomains unloaded since the start of the application.

For an App Service plan, the available metrics are:

 Note

App Service plan metrics are available only for plans in BasicStandard, and Premium tiers.

MetricDescription
CPU PercentageThe average CPU used across all instances of the plan.
Memory PercentageThe average memory used across all instances of the plan.
Data InThe average incoming bandwidth used across all instances of the plan.
Data OutThe average outgoing bandwidth used across all instances of the plan.
Disk Queue LengthThe 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.
Http Queue LengthThe 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.

https://learn.microsoft.com/en-us/azure/app-service/web-sites-monitor

Leave a Comment