Health score. A health score provides real-time insight into the overall health and performance of your monitored entities. The health score is calculated based on anomalies detected for the entity, alerts triggered for the entity's metrics, and the status of the entity. The health score is displayed as a single numerical value that ranges from a Good (70-100) to Moderate (40-69) to Bad (0-39) distinction.

To view the health score for Azure App Service entities in the Metrics Explorer, filter the sw.metrics.healthscore metric by entity_types and select azureappservice.

The average number of connections established by an application in Azure App Service.

Total App Domains. The average number of AppDomains loaded in this application.

The number of application domains that have been unloaded in an Azure App Service environment, which can be useful for monitoring app lifecycle events.

The number of garbage collection events for Generation 1 objects in an Azure App Service instance.

The number of garbage collection events for Generation 2 objects in an Azure App Service instance.

CPU Time. The total amount of CPU consumed by the app, in seconds.

The number of assemblies currently loaded across all application domains in an Azure App Service instance.

The total number of function executions in an Azure Functions app, providing insight into function activity and usage.

The number of open file handles in an Azure App Service environment. This metric helps monitor resource usage and potential file access issues.

Tracks HTTP 101 responses, which indicate protocol switching (for example, upgrading from HTTP to WebSockets).

Http2xx. The total number of requests resulting in an HTTP status code greater than or equal to 200 but less than 300.

HTTP 3xx responses, which indicate redirection. These status codes signal that the requested resource has moved to a different location.

HTTP 401 responses, which indicate unauthorized access. This occurs when authentication credentials are missing or invalid.

HTTP 403 responses, which indicate forbidden access. This happens when a request is denied due to insufficient permissions or security restrictions.

HTTP 404 responses, which indicate that the requested resource was not found. This can occur when a URL is incorrect or the resource has been removed.

HTTP 406 responses, which indicate that the requested format is not acceptable. This happens when the server cannot provide content in the format specified by the request.

Http4xx. The total number of requests resulting in an HTTP status code greater than or equal to 400 but less than 500.

Http5xx. The total number of requests resulting in an HTTP status code greater than or equal to 500 but less than 600.

Bytes Received. The total amount of incoming bandwidth consumed by the app.

Bytes Sent. The total amount of outgoing bandwidth consumed by the app.

The rate at which the app process issues bytes to I/O operations that do not involve data transfer, such as control operations.

The rate at which the app process issues I/O operations that are not read or write operations.

IoReadBytesPerSecond. The number of bytes per second the app is reading from I/O operations.

The number of read operations performed by the app process.

IO Write Bytes Per Second. The number of bytes per second the app is writing to I/O operations.

The number of write operations performed by the app process.

Memory Working Set. The current amount of memory used by the app.

Average Memory Working Set. The average amount of memory used by the app, in megabytes.

The amount of memory allocated by the app process that cannot be shared with other processes. This includes allocated memory, local variables, heap memory, and other runtime data.

Requests In Application Queue. The average number of requests in the application request queue.

Requests. The total number of requests regardless of their resulting HTTP status code.

Average Response Time. The average time taken for the app to serve requests, in seconds.

Threads. The average number of threads currently active in the app process.