review cx

Author: v-thepet

articles/app-service/monitor-app-service-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Azure App Service monitoring data reference
 description: This article contains important reference material you need when you monitor Azure App Service.
-ms.date: 02/29/2024
+ms.date: 03/04/2024
 ms.custom: horz-monitor
 ms.topic: reference
 author: msangapu-msft
@@ -33,78 +33,10 @@ The following tables list the automatically collected platform metrics for App S
 | App Service Environment Worker Pools | [Microsoft.Web/hostingEnvironments/workerPools](/azure/azure-monitor/reference/supported-metrics/microsoft-web-hostingenvironments-workerpools-metrics)
 
 >[!NOTE]
->Azure App Service, Functions, and Logic Apps share the Microsoft.Web/sites namespace dating back to when they were a single service. Refer to the following list or the **Metric** column in the overall linked table to see which metrics apply to which services. The **Metrics** interface in the Azure portal for each service shows only the metrics that apply to that service.
-
-For web apps, the available metrics in Microsoft.Web/sites are:
-
-- Response Time
-- Average Response Time (deprecated)
-- Average memory working set
-- Connections
-- CPU Time
-- Current Assemblies
-- Data In
-- Data Out
-- File System Usage
-- Gen 0 Garbage Collections
-- Gen 1 Garbage Collections
-- Gen 2 Garbage Collections
-- Handle Count
-- Health Check Status
-- Http 2xx
-- Http 3xx
-- Http 401
-- Http 403
-- Http 404
-- Http 406
-- Http 4xx
-- Http Server Errors
-- IO Other Bytes Per Second
-- IO Other Operations Per Second
-- IO Read Bytes Per Second
-- IO Read Operations Per Second
-- IO Write Bytes Per Second
-- IO Write Operations Per Second
-- Memory working set
-- Private Bytes
-- Requests
-- Requests In Application Queue
-- Thread Count
-- Total App Domains
-- Total App Domains Unloaded
-
-For an App Service plan, the metrics in Microsoft.Web/serverfarms are:
-
-- Data In
-- Data Out
-- CPU Percentage
-- Disk Queue Length
-- Http Queue Length
-- Memory Percentage
-- Socket Count for Inbound Requests
-- Socket Count for Loopback Connections
-- Socket Count of Outbound Requests
-- Established Socket Count for Outbound Requests
-- Time Wait Socket Count for Outbound Requests
-- TCP Close Wait
-- TCP Closing
-- TCP Established
-- TCP Fin Wait 1
-- TCP Fin Wait 2
-- TCP Last Ack
-- TCP Syn Received
-- TCP Syn Sent
-- TCP Time Wait
-
-> [!NOTE]
-> App Service plan metrics are available only for plans in *Basic*, *Standard*, and *Premium* tiers.
-
-Two metrics reflect CPU usage:
-
-- CPU Time
-- CPU percentage
-
-These metrics are useful for apps hosted in Basic, Standard, and Premium plans, because they can be scaled out. CPU percentage is a good indication of the overall usage across all instances.
+>Azure App Service, Functions, and Logic Apps share the Microsoft.Web/sites namespace dating back to when they were a single service. Refer to the **Metric** column in the [Microsoft.Web/sites](/azure/azure-monitor/reference/supported-metrics/microsoft-web-sites-metrics) table to see which metrics apply to which services. The **Metrics** interface in the Azure portal for each service shows only the metrics that apply to that service.
+
+>[!NOTE]
+>App Service Plan metrics are available only for plans in *Basic*, *Standard*, and *Premium* tiers.
 
 [!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
 [!INCLUDE [horz-monitor-ref-metrics-dimensions](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]

articles/app-service/web-sites-monitor.md

@@ -64,7 +64,69 @@ You can increase or remove quotas from your app by upgrading your App Service pl
 
 Metrics provide information about the app or the App Service plan's behavior.
 
-For a list of the metrics that apply to apps and App Service plans, see [Supported metrics for Microsoft.Web](monitor-app-service-reference.md#supported-metrics-for-microsoftweb).
+For an app, the available metrics are:
+
+| Metric | Description |
+| --- | --- |
+| **Response Time** | The 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 set** | The average amount of memory used by the app, in megabytes (MiB). |
+| **Connections** | The 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 Time** | The amount of CPU consumed by the app, in seconds. For more information about this metric, see [CPU time vs CPU percentage](#cpu-time-vs-cpu-percentage). |
+| **Current Assemblies** | The current number of Assemblies loaded across all AppDomains in this application. |
+| **Data In** | The amount of incoming bandwidth consumed by the app, in MiB. |
+| **Data Out** | The amount of outgoing bandwidth consumed by the app, in MiB. |
+| **File System Usage** | The amount of usage in bytes by storage share. |
+| **Gen 0 Garbage Collections** | The 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 Collections** | The 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 Collections** | The number of times the generation 2 objects are garbage collected since the start of the app process.|
+| **Handle Count** | The total number of handles currently open by the app process.|
+| **Health Check Status** | The average health status across the application's instances in the App Service Plan.|
+| **Http 2xx** | The count of requests resulting in an HTTP status code ≥ 200 but < 300. |
+| **Http 3xx** | The count of requests resulting in an HTTP status code ≥ 300 but < 400. |
+| **Http 401** | The count of requests resulting in HTTP 401 status code. |
+| **Http 403** | The count of requests resulting in HTTP 403 status code. |
+| **Http 404** | The count of requests resulting in HTTP 404 status code. |
+| **Http 406** | The count of requests resulting in HTTP 406 status code. |
+| **Http 4xx** | The count of requests resulting in an HTTP status code ≥ 400 but < 500. |
+| **Http Server Errors** | The count of requests resulting in an HTTP status code ≥ 500 but < 600. |
+| **IO Other Bytes Per Second** | The 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 Second** | The rate at which the app process is issuing I/O operations that aren't read or write operations.|
+| **IO Read Bytes Per Second** | The rate at which the app process is reading bytes from I/O operations.|
+| **IO Read Operations Per Second** | The rate at which the app process is issuing read I/O operations.|
+| **IO Write Bytes Per Second** | The rate at which the app process is writing bytes to I/O operations.|
+| **IO Write Operations Per Second** | The rate at which the app process is issuing write I/O operations.|
+| **Memory working set** | The current amount of memory used by the app, in MiB. |
+| **Private Bytes** | Private Bytes is the current size, in bytes, of memory that the app process has allocated that can't be shared with other processes.|
+| **Requests** | The total number of requests regardless of their resulting HTTP status code. |
+| **Requests In Application Queue** | The number of requests in the application request queue.|
+| **Thread Count** | The number of threads currently active in the app process.|
+| **Total App Domains** | The current number of AppDomains loaded in this application.|
+| **Total App Domains Unloaded** | The 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 *Basic*, *Standard*, and *Premium* tiers.
+> 
+| Metric | Description |
+| --- | --- |
+| **CPU Percentage** | The average CPU used across all instances of the plan. |
+| **Memory Percentage** | The average memory used across all instances of the plan. |
+| **Data In** | The average incoming bandwidth used across all instances of the plan. |
+| **Data Out** | The average outgoing bandwidth used across all instances of the plan. |
+| **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. |
+| **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. |
+
+### CPU time vs CPU percentage
+<!-- To do: Fix Anchor (#CPU-time-vs.-CPU-percentage) -->
+
+There are two metrics that reflect CPU usage:
+
+**CPU Time**: Useful for apps hosted in Free or Shared plans, because one of their quotas is defined in CPU minutes used by the app.
+
+**CPU percentage**: Useful for apps hosted in Basic, Standard, and Premium plans, because they can be scaled out. CPU percentage is a good indication of the overall usage across all instances.
 
 ## Metrics granularity and retention policy
 Metrics for an app and app service plan are logged and aggregated by the service and [retained according to these rules](../azure-monitor/essentials/data-platform-metrics.md#retention-of-metrics).