Merge pull request #99882 from btardif/master

updating outdated screenshot and information about metrics

Author: ktoliver

articles/app-service/media/web-sites-monitor/metrics.png

@@ -12,9 +12,9 @@ ms.custom: seodec18
 ---
 # Monitor apps in Azure App Service
 [Azure App Service](https://go.microsoft.com/fwlink/?LinkId=529714) provides
-built-in monitoring functionality for web apps, mobile back ends, and API apps in the [Azure portal](https://portal.azure.com).
+built-in monitoring functionality for web apps, mobile, and API apps in the [Azure portal](https://portal.azure.com).
 
-In the Azure portal, you can review *quotas* and *metrics* for an app and App Service plan, and set up *alerts* and *auto-scaling* that are based metrics.
+In the Azure portal, you can review *quotas* and *metrics* for an app and App Service plan, and set up *alerts* and *autoscaling* that are based metrics.
 
 ## Understand quotas
 
@@ -73,7 +73,7 @@ For an app, the available metrics are:
 | **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** | Percentage of filesystem quota consumed by the app . |
+| **File System Usage** | Percentage of filesystem quota consumed by the app. |
 | **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.|
@@ -86,14 +86,14 @@ For an app, the available metrics are:
 | **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 do not involve data, such as control operations.|
-| **IO Other Operations Per Second** | The rate at which the app process is issuing I/O operations that are not read or write operations.|
+| **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 cannot be shared with other processes.|
+| **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.|
@@ -113,7 +113,7 @@ For an App Service plan, the available metrics are:
 | **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 due to excessive disk I/O. |
+| **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
@@ -128,9 +128,9 @@ There are two metrics that reflect CPU usage:
 ## Metrics granularity and retention policy
 Metrics for an app and app service plan are logged and aggregated by the service, with the following granularities and retention policies:
 
-* **Minute** granularity metrics are retained for 30 hours.
-* **Hour** granularity metrics are retained for 30 days.
-* **Day** granularity metrics are retained for 30 days.
+* **Minute** granularity metrics are kept for 30 hours.
+* **Hour** granularity metrics are kept for 30 days.
+* **Day** granularity metrics are kept for 30 days.
 
 ## Monitoring quotas and metrics in the Azure portal
 To review the status of the various quotas and metrics that affect an app, go to the [Azure portal](https://portal.azure.com).
@@ -144,19 +144,16 @@ To find quotas, select **Settings** > **Quotas**. On the chart, you can review:
 1. Its current value.
 
 ![Metric chart in the Azure portal][metrics]
-You can access metrics directly from the **Resource** page. To customize the chart: 
-1. Select the chart.
-1. Select **Edit chart**.
-1. Edit the **Time Range**.
-1. Edit the **Chart type**.
-1. Edit the metrics you want to display.  
+You can access metrics directly from the resource **Overview** page. Here you'll see charts representing some of the apps metrics.
+
+Clicking on any of those charts will take you to the metrics view where you can create custom charts, query different metrics and much more. 
 
 To learn more about metrics, see [Monitor service metrics](../monitoring-and-diagnostics/insights-how-to-customize-monitoring.md).
 
 ## Alerts and autoscale
 Metrics for an app or an App Service plan can be hooked up to alerts. For more information, see [Receive alert notifications](../monitoring-and-diagnostics/insights-alerts-portal.md).
 
-App Service apps hosted in Basic, Standard, or Premium App Service plans support autoscale. With autoscale, you can configure rules that monitor the App Service plan metrics. Rules can increase or decrease the instance count, which can provide additional resources as needed. Rules can also help you save money when the app is over-provisioned.
+App Service apps hosted in Basic or higher App Service plans support autoscale. With autoscale, you can configure rules that monitor the App Service plan metrics. Rules can increase or decrease the instance count, which can provide additional resources as needed. Rules can also help you save money when the app is over-provisioned.
 
 For more information about autoscale, see [How to scale](../monitoring-and-diagnostics/insights-how-to-scale.md) and [Best practices for Azure Monitor autoscaling](../azure-monitor/platform/autoscale-best-practices.md).