Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into heidist-search

Author: HeidiSteen

.openpublishing.redirection.json

@@ -355,7 +355,7 @@
       "redirect_url": "/azure/machine-learning/data-science-virtual-machine/reference-deprecation",
       "redirect_document_id": true
     },
-    
+
     {
       "source_path": "articles/machine-learning/service/how-to-understand-accuracy-metrics.md",
       "redirect_url": "/azure/machine-learning/service/how-to-understand-automated-ml",
@@ -50683,6 +50683,16 @@
       "source_path": "articles/chef/index.yml",
       "redirect_url": "/azure/developer/chef/",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/security/fundamentals/database-security-overview.md",
+      "redirect_url": "/azure/sql-database/sql-database-security-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/security/fundamentals/database-best-practices.md",
+      "redirect_url": "/azure/sql-database/sql-database-security-best-practice",
+      "redirect_document_id": false
     }
   ]
 }

articles/app-service/environment/create-ilb-ase.md

@@ -56,6 +56,9 @@ To create an ILB ASE:
 
     ![ASE creation](media/creating_and_using_an_internal_load_balancer_with_app_service_environment/createilbase.png)
 
+> [!NOTE]
+> The App Service Environment name must be no more than 37 characters.
+
 6. Select Networking
 
 7. Select or create a Virtual Network. If you create a new VNet here, it will be defined with an address range of 192.168.250.0/23. To create a VNet with a different address range or in a different resource group than the ASE, use the Azure Virtual Network creation portal. 
@@ -66,6 +69,7 @@ To create an ILB ASE:
 
 7. Select **Review and Create** then select **Create**.
 
+
 ## Create an app in an ILB ASE ##
 
 You create an app in an ILB ASE in the same way that you create an app in an ASE normally.

articles/cosmos-db/TOC.yml

@@ -1037,6 +1037,8 @@
         href: monitor-cosmos-db.md
       - name: Monitor server-side latency
         href: monitor-server-side-latency.md
+      - name: Monitor request unit usage
+        href: monitor-request-unit-usage.md
       - name: Monitor with diagnostic logs
         href: cosmosdb-monitor-resource-logs.md
       - name: Audit control plane logs

articles/cosmos-db/media/monitor-request-unit-usage/monitor-metrics-blade.png

@@ -0,0 +1,61 @@
+---
+title: Monitor the throughput usage of an operation in Azure Cosmos DB 
+description: Learn how to monitor the throughput or request unit usage of an operation in Azure Cosmos DB. Owners of an Azure Cosmos DB account can understand which operations are taking more Request units. 
+ms.service:  cosmos-db
+ms.topic: conceptual
+author: kanshiG    
+ms.author: govindk
+ms.date: 04/09/2020
+---
+
+# How to monitor throughput or request unit usage of an operation in Azure Cosmos DB
+
+Azure Monitor for Azure Cosmos DB provides a metrics view to monitor your account and create dashboards. The Azure Cosmos DB metrics are collected by default, this feature does not require you to enable or configure anything explicitly. The **Total Request Units** metric is used to get the request units usage for different types of operations. Later you can analyze which operations used most of the throughput. By default, the throughput data is aggregated at one-minute interval. However, you can change the aggregation unit by changing the time granularity option.
+
+There are two ways to analyze the request unit usage data:
+
+* Within the given time interval which operations are taking more request units.
+* Which operations in general dominate your workload by consuming more request units.
+This analysis allows you to focus on operations such as insert, upsert and look at their indexing. You can find out if you are over/under indexing specific fields and modify the [indexing policy](index-policy.md#include-exclude-paths) to include or exclude the paths.
+
+If you notice certain queries are taking more request units, you can take actions such as:
+
+* Reconsider if you are requesting the right amount of data.
+* Modify the query to use index with filter clause.
+* Perform less expensive UDF function calls.
+* Define partition keys to minimize the fan out of query into different partitions.
+* You can also use the query metrics returned in the call response, the diagnostic log details and refer to [query performance tuning](sql-api-query-metrics.md) article to learn more about the query execution.
+* You can start from sum and then look at avg utilization using the right dimension.
+
+## View the total request unit usage metric
+
+1. Sign in to the [Azure portal](https://portal.azure.com/).
+
+1. Select **Monitor** from the left-hand navigation bar and select **Metrics**.
+
+   ![Metrics pane in Azure Monitor](./media/monitor-request-unit-usage/monitor-metrics-blade.png)
+
+1. From the **Metrics** pane > **Select a resource** > choose the required **subscription**, and **resource group**. For the **Resource type**, select **Azure Cosmos DB accounts**, choose one of your existing Azure Cosmos accounts, and select **Apply**.
+
+   ![Choose the Azure Cosmos DB account to view metrics](./media/monitor-request-unit-usage/select-cosmos-db-account.png)
+
+1. Next select the **Total Request Units** metric from the list of available metrics. To learn in detail about all the available metrics in this list, see the [Metrics by category](monitor-cosmos-db-reference.md) article. In this example, let's select **Total Request Units** and **Avg** as the aggregation value. In addition to these details, you can also select the **Time range** and **Time granularity** of the metrics. At max, you can view metrics for the past 30 days.  After you apply the filter, a chart is displayed based on your filter. You can see the average number of request units consumed per minute for the selected period.  
+
+   ![Choose a metric from the Azure portal](./media/monitor-request-unit-usage/request-unit-usage-metric.png)
+
+## Filters for request unit usage
+
+You can also filter metrics and get the charts displayed by a specific **CollectionName**, **DatabaseName**, **OperationType**, **Region**, **Status**, and **StatusCode**. The **Add filter** and **Apply splitting** options allows you to filter the request unit usage and group the metrics.
+
+To get the request unit usage of each operation either by total(sum) or average, select **Apply splitting** and choose **Operation type** and the filter value as shown in the following image:
+
+   ![Cosmos DB Request units for operations in Azure monitor](./media/monitor-request-unit-usage/request-unit-usage-operations.png)
+
+If you want to see the request unit usage by collection, select **Apply splitting** and choose the collection name as a filter. You will see a chat like the following with a choice of collections within the dashboard. You can then select a specific collection name to view more details:
+
+   ![Cosmos DB Request units for all operations by the collection in Azure monitor](./media/monitor-request-unit-usage/request-unit-usage-collection.png)
+
+## Next steps
+
+* Monitor Azure Cosmos DB data by using [diagnostic settings](cosmosdb-monitor-resource-logs.md) in Azure.
+* [Audit Azure Cosmos DB control plane operations](audit-control-plane-logs.md)

articles/cosmos-db/media/monitor-request-unit-usage/request-unit-usage-collection.png

@@ -20,7 +20,7 @@ If you see unusually large latency for point operations such as:
 
 You can look up the diagnostic log to see the size of data returned. If you see a sustained high latency for query operations, you can look up the diagnostic log for size of data returned, [throughput or RU/s](cosmosdb-monitor-resource-logs.md#diagnostic-queries) used, or the number of such operations in a given period. This way, you can debug the server-side latency issues.
 
-## View server-side latency metric
+## View the server-side latency metric
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 
@@ -30,15 +30,15 @@ You can look up the diagnostic log to see the size of data returned. If you see
 
 1. From the **Metrics** pane > **Select a resource** > choose the required **subscription**, and **resource group**. For the **Resource type**, select **Azure Cosmos DB accounts**, choose one of your existing Azure Cosmos accounts, and select **Apply**.
 
-   ![Choose a Cosmos DB account to view metrics](./media/monitor-server-side-latency/select-cosmos-db-account.png)
+   ![Choose the Azure Cosmos DB account to view metrics](./media/monitor-server-side-latency/select-cosmos-db-account.png)
 
-1. Next select the **Server Side Latency**  metric from the list of available metrics. To learn in detail about all the available metrics in this list, see the [Metrics by category](monitor-cosmos-db-reference.md) article. In this example, let's select **Server Side Latency** and **Avg** as the aggregation value. In addition to these details, you can also select the **Time range** and **Time granularity** of the metrics. At max, you can view metrics for the past 30 days.  After you apply the filter, a chart is displayed based on your filter. You can see the average number of request units consumed per minute for the selected period.  
+1. Next select the **Server Side Latency**  metric from the list of available metrics. To learn in detail about all the available metrics in this list, see the [Metrics by category](monitor-cosmos-db-reference.md) article. In this example, let's select **Server Side Latency** and **Avg** as the aggregation value. In addition to these details, you can also select the **Time range** and **Time granularity** of the metrics. At max, you can view metrics for the past 30 days.  After you apply the filter, a chart is displayed based on your filter. You can see the server-side latency per minute for the selected period.  
 
    ![Choose the Server-Side Latency metric from the Azure portal](./media/monitor-server-side-latency/server-side-latency-metric.png)
 
 ## Filters for server-side latency
 
-You can also filter metrics and the chart displayed by a specific **CollectionName**, **ConnectionMode**, **DatabaseName**, **OperationType**, **Region**, and **PublicAPIType**. 
+You can also filter metrics and get the charts displayed by a specific **CollectionName**, **ConnectionMode**, **DatabaseName**, **OperationType**, **Region**, and **PublicAPIType**. 
 
 To filter the metrics, select **Add filter** and choose the required property such as **PublicAPIType** and select the value **sql**. Add another filter for **OperationType**. The graph then displays the server-side latency for different operations during the selected period. The operations executed via Stored procedure are not logged so they are not available under the OperationType metric.
 
@@ -50,5 +50,5 @@ You can also group the metrics by using the **Apply splitting** option.
 
 ## Next steps
 
-* Monitor Azure Cosmos DB data by using [diagnostic settings](cosmosdb-monitor-resource-logs.md) in Azure
+* Monitor Azure Cosmos DB data by using [diagnostic settings](cosmosdb-monitor-resource-logs.md) in Azure.
 * [Audit Azure Cosmos DB control plane operations](audit-control-plane-logs.md)