Merge pull request #110483 from SnehaGunda/breadcrumb

Adding monitor server side latency doc

Author: GitHubber17

articles/cosmos-db/TOC.yml

@@ -1033,6 +1033,8 @@
       items:
       - name: Monitor Cosmos DB
         href: monitor-cosmos-db.md
+      - name: Monitor server-side latency
+        href: monitor-server-side-latency.md
       - name: Monitor with diagnostic logs
         href: cosmosdb-monitor-resource-logs.md
       - name: Audit control plane logs

articles/cosmos-db/media/monitor-cosmos-db/serverside-latency-metric.png

@@ -43,7 +43,7 @@ The following sections build on this article by describing the specific data gat
 
    ![Choose a Cosmos DB account to view metrics](./media/monitor-cosmos-db/select-cosmosdb-account.png)
 
-1. Next you can select a metric from the list of available metrics. You can select metrics specific to request units, storage, latency, availability, Cassandra, and others. 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 **Request units** and **Avg** as the aggregation value.
+1. Next you can select a metric from the list of available metrics. You can select metrics specific to request units, storage, latency, availability, Cassandra, and others. 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 **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.  
 
@@ -59,10 +59,6 @@ You can group metrics by using the **Apply splitting** option. For example, you
 
 ![Add apply splitting filter](./media/monitor-cosmos-db/apply-metrics-splitting.png)
 
-Here is another example to view the server-side latency metrics for a specific database, container, or an operation:
-
-![Server-side latency metrics](./media/monitor-cosmos-db/serverside-latency-metric.png)
-
 ## Monitoring data collected from Azure Cosmos DB
 
 Azure Cosmos DB collects the same kinds of monitoring data as other Azure resources which are described in [Monitoring data from Azure resources](../azure-monitor/insights/monitor-azure-resource.md#monitoring-data). See [Azure Cosmos DB monitoring data reference](monitor-cosmos-db-reference.md) for a detailed reference of the logs and metrics created by Azure Cosmos DB.

articles/cosmos-db/media/monitor-server-side-latency/monitor-metrics-blade.png

@@ -0,0 +1,54 @@
+---
+title: How to monitor the server-side latency for operations in Azure Cosmos DB 
+description: Learn how to monitor server latency for operations in Azure Cosmos DB account or a container. Owners of an Azure Cosmos DB account can understand the server-side latency issues with your Azure Cosmos accounts.
+ms.service:  cosmos-db
+ms.topic: conceptual
+author: kanshiG  
+ms.author: govindk
+ms.date: 04/07/2020
+---
+
+# How to monitor the server-side latency for operations in an Azure Cosmos DB container or account
+
+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 server-side latency metric is used to view the server-side latency of an operation. Azure Cosmos DB provides SLA of less than 10 ms for point read/write operations with direct connectivity. For point read and write operations, the SLAs are calculated as detailed in the [SLA document](https://azure.microsoft.com/support/legal/sla/cosmos-db/v1_3/).
+
+If you see unusually large latency for point operations such as:
+
+* A get or set operation with partition key and ID in direct mode
+* A read or write operation or
+* A query
+
+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
+
+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-server-side-latency/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 a Cosmos DB account to view metrics](./media/monitor-server-side-latency/select-cosmosdb-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.  
+
+   ![Choose the Server-Side Latency metric from the Azure portal](./media/monitor-server-side-latency/serverside-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**. 
+
+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.
+
+The **Server Side Latency** metrics for each operation are displayed as shown in the following image:
+
+![Filters for server-side latency metrics](./media/monitor-server-side-latency/serverside-latency-filters.png)
+
+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
+* [Audit Azure Cosmos DB control plane operations](audit-control-plane-logs.md)