Merge pull request #217586 from seesharprun/cosmos-enable-full-text-query

Cosmos DB | Added instructions to enable full-text query using Azure CLI

Author: tamarakhader

articles/cosmos-db/.openpublishing.redirection.cosmos-db.json

@@ -3105,6 +3105,11 @@
       "redirect_url": "/azure/cosmos-db/advanced-queries",
       "redirect_document_id": true
     },
+    {
+      "source_path_from_root": "/articles/cosmos-db/advanced-queries.md",
+      "redirect_url": "/azure/cosmos-db/nosql/diagnostic-queries",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/cosmos-db/cosmos-db-reserved-capacity.md",
       "redirect_url": "/azure/cosmos-db/reserved-capacity",

articles/cosmos-db/cassandra/TOC.yml

@@ -352,8 +352,6 @@
           href: error-codes-solution.md
         - name: Monitor and debug with insights in API for Apache Cassandra
           href: monitor-insights.md
-        - name: Advanced diagnostics for API for Apache Cassandra
-          href: diagnostic-queries.md
     - name: Manage Azure Cosmos DB resources
       items:
         - name: Manage an Azure Cosmos DB account
@@ -432,10 +430,10 @@
               href: ../monitor-resource-logs.md
             - name: Troubleshoot issues using basic queries
               href: ../monitor-logs-basic-queries.md
-            - name: Troubleshoot issues using advanced queries
-              href: ../advanced-queries.md
             - name: Audit control plane logs
               href: ../audit-control-plane-logs.md
+            - name: Troubleshoot issues with advanced diagnostics queries
+              href: diagnostic-queries.md
         - name: Configure alerts
           items:
             - name: Create alert on metrics

articles/cosmos-db/cassandra/diagnostic-queries.md

@@ -274,8 +274,6 @@
           href: headers.md
         - name: Limits
           href: limits.md
-        - name: Monitor using Diagnostics Logs
-          href: diagnostic-queries.md
     - name: Use developer tools
       items:
         - name: Develop locally with emulator
@@ -398,10 +396,10 @@
               href: ../monitor-resource-logs.md
             - name: Troubleshoot issues using basic queries
               href: ../monitor-logs-basic-queries.md
-            - name: Troubleshoot issues using advanced queries
-              href: ../advanced-queries.md
             - name: Audit control plane logs
               href: ../audit-control-plane-logs.md
+            - name: Troubleshoot issues with advanced diagnostics queries
+              href: diagnostic-queries.md
         - name: Configure alerts
           items:
             - name: Create alert on metrics

articles/cosmos-db/gremlin/TOC.yml

@@ -1,43 +1,32 @@
 ---
-title: Troubleshoot issues with advanced diagnostics queries for API for Gremlin
-titleSuffix: Azure Cosmos DB
-description: Learn how to query diagnostics logs for troubleshooting data stored in Azure Cosmos DB for the API for Gremlin.
-author: StefArroyo
-services: cosmos-db
+title: Troubleshoot issues with advanced diagnostics queries with Azure Cosmos DB for Apache Gremlin
+description: Learn how to query diagnostics logs for troubleshooting data stored in Azure Cosmos DB for Apache Gremlin.
+author: seesharprun
+ms.author: sidandrews
+ms.reviewer: esarroyo
 ms.service: cosmos-db
 ms.custom: ignite-2022
 ms.topic: how-to
-ms.date: 06/12/2021
-ms.author: esarroyo 
+ms.date: 11/08/2022
 ---
 
-# Troubleshoot issues with advanced diagnostics queries for the API for Gremlin
+# Troubleshoot issues with advanced diagnostics queries with Azure Cosmos DB for Apache Gremlin
 
 [!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin](../includes/appliesto-nosql-mongodb-cassandra-gremlin.md)]
 
-> [!div class="op_single_selector"]
-> * [API for NoSQL](../advanced-queries.md)
-> * [API for MongoDB](../mongodb/diagnostic-queries.md)
-> * [API for Cassandra](../cassandra/diagnostic-queries.md)
-> * [API for Gremlin](diagnostic-queries.md)
->
+[!INCLUDE[Diagnostic queries selector](../includes/diagnostic-queries-selector.md)]
 
 In this article, we'll cover how to write more advanced queries to help troubleshoot issues with your Azure Cosmos DB account by using diagnostics logs sent to **Azure Diagnostics (legacy)** and **resource-specific (preview)** tables.
 
-For Azure Diagnostics tables, all data is written into one single table. Users specify which category they want to query. If you want to view the full-text query of your request, see [Monitor Azure Cosmos DB data by using diagnostic settings in Azure](../monitor-resource-logs.md) to learn how to enable this feature.
-
-For [resource-specific tables](../monitor-resource-logs.md), data is written into individual tables for each category of the resource. We recommend this mode because it:
-
-- Makes it much easier to work with the data. 
-- Provides better discoverability of the schemas.
-- Improves performance across both ingestion latency and query times.
+[!INCLUDE[Diagnostic tables](../includes/diagnostics-tables.md)]
 
 ## Common queries
+
 Common queries are shown in the resource-specific and Azure Diagnostics tables.
 
 ### Top N(10) Request Unit (RU) consuming requests or queries in a specific time frame
 
-# [Resource-specific](#tab/resource-specific)
+#### [Resource-specific](#tab/resource-specific)
 
    ```Kusto
    let topRequestsByRUcharge = CDBDataPlaneRequests 
@@ -50,7 +39,8 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | order by RequestCharge desc
    | take 10
    ```
-# [Azure Diagnostics](#tab/azure-diagnostics)
+
+#### [Azure Diagnostics](#tab/azure-diagnostics)
 
    ```Kusto
    let topRequestsByRUcharge = AzureDiagnostics
@@ -63,12 +53,14 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | project databasename_s , collectionname_s , piiCommandText_s , requestCharge_s, TimeGenerated
    | order by requestCharge_s desc
    | take 10
-   ```    
+   ```
+
 ---
 
-### Requests throttled (statusCode = 429) in a specific time window 
+### Requests throttled (statusCode = 429) in a specific time window
+
+#### [Resource-specific](#tab/resource-specific)
 
-# [Resource-specific](#tab/resource-specific)
    ```Kusto
    let throttledRequests = CDBDataPlaneRequests
    | where StatusCode == "429"
@@ -78,7 +70,9 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | join kind=inner throttledRequests on ActivityId
    | project DatabaseName , CollectionName , PIICommandText , OperationName, TimeGenerated
    ```
-# [Azure Diagnostics](#tab/azure-diagnostics)
+
+#### [Azure Diagnostics](#tab/azure-diagnostics)
+
    ```Kusto
    let throttledRequests = AzureDiagnostics
    | where Category == "DataPlaneRequests"
@@ -89,12 +83,14 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | project piiCommandText_s, activityId_g, databasename_s , collectionname_s
    | join kind=inner throttledRequests on activityId_g
    | project databasename_s , collectionname_s , piiCommandText_s , OperationName, TimeGenerated
-   ```    
+   ```
+
 ---
 
 ### Queries with large response lengths (payload size of the server response)
 
-# [Resource-specific](#tab/resource-specific)
+#### [Resource-specific](#tab/resource-specific)
+
    ```Kusto
    let operationsbyUserAgent = CDBDataPlaneRequests
    | project OperationName, DurationMs, RequestCharge, ResponseLength, ActivityId;
@@ -106,7 +102,8 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | order by max_ResponseLength desc
    ```
 
-# [Azure Diagnostics](#tab/azure-diagnostics)
+#### [Azure Diagnostics](#tab/azure-diagnostics)
+
    ```Kusto
    let operationsbyUserAgent = AzureDiagnostics
     | where Category=="DataPlaneRequests"
@@ -117,12 +114,14 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | join kind=inner operationsbyUserAgent on activityId_g
    | summarize max(responseLength_s1) by piiCommandText_s
    | order by max_responseLength_s1 desc
-   ```    
+   ```
+
 ---
 
 ### RU consumption by physical partition (across all replicas in the replica set)
 
-# [Resource-specific](#tab/resource-specific)
+#### [Resource-specific](#tab/resource-specific)
+
    ```Kusto
    CDBPartitionKeyRUConsumption
    | where TimeGenerated >= now(-1d)
@@ -133,7 +132,9 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | summarize sum(todouble(RequestCharge)) by toint(PartitionKeyRangeId)
    | render columnchart
    ```
-# [Azure Diagnostics](#tab/azure-diagnostics)
+
+#### [Azure Diagnostics](#tab/azure-diagnostics)
+
    ```Kusto
    AzureDiagnostics
    | where TimeGenerated >= now(-1d)
@@ -144,12 +145,14 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    //| where operationType_s == 'Create'
    | summarize sum(todouble(requestCharge_s)) by toint(partitionKeyRangeId_s)
    | render columnchart  
-   ```    
+   ```
+
 ---
 
 ### RU consumption by logical partition (across all replicas in the replica set)
 
-# [Resource-specific](#tab/resource-specific)
+#### [Resource-specific](#tab/resource-specific)
+
    ```Kusto
    CDBPartitionKeyRUConsumption
    | where TimeGenerated >= now(-1d)
@@ -160,7 +163,9 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | summarize sum(todouble(RequestCharge)) by PartitionKey, PartitionKeyRangeId
    | render columnchart  
    ```
-# [Azure Diagnostics](#tab/azure-diagnostics)
+
+#### [Azure Diagnostics](#tab/azure-diagnostics)
+
    ```Kusto
    AzureDiagnostics
    | where TimeGenerated >= now(-1d)
@@ -172,8 +177,10 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | summarize sum(todouble(requestCharge_s)) by partitionKey_s, partitionKeyRangeId_s
    | render columnchart  
    ```
+
 ---
 
-## Next steps 
-* For more information on how to create diagnostic settings for Azure Cosmos DB, see [Create diagnostic settings](../monitor-resource-logs.md).
-* For detailed information about how to create a diagnostic setting by using the Azure portal, the Azure CLI, or PowerShell, see [Create diagnostic settings to collect platform logs and metrics in Azure](../../azure-monitor/essentials/diagnostic-settings.md).
+## Next steps
+
+- For more information on how to create diagnostic settings for Azure Cosmos DB, see [Create diagnostic settings](../monitor-resource-logs.md).
+- For detailed information about how to create a diagnostic setting by using the Azure portal, the Azure CLI, or PowerShell, see [Create diagnostic settings to collect platform logs and metrics in Azure](../../azure-monitor/essentials/diagnostic-settings.md).

articles/cosmos-db/gremlin/diagnostic-queries.md

@@ -0,0 +1,17 @@
+---
+author: seesharprun
+ms.author: sidandrews
+ms.reviewer: esarroyo
+ms.service: cosmos-db
+ms.topic: include
+ms.date: 11/08/2022
+ms.custom: include file
+---
+
+> [!div class="op_single_selector"]
+>
+> * [API for NoSQL](../nosql/diagnostic-queries.md)
+> * [API for MongoDB](../mongodb/diagnostic-queries.md)
+> * [API for Apache Cassandra](../cassandra/diagnostic-queries.md)
+> * [API for Apache Gremlin](../gremlin/diagnostic-queries.md)
+>

articles/cosmos-db/includes/diagnostic-queries-selector.md

@@ -0,0 +1,17 @@
+---
+author: seesharprun
+ms.author: sidandrews
+ms.reviewer: esarroyo
+ms.service: cosmos-db
+ms.topic: include
+ms.date: 11/08/2022
+ms.custom: include file
+---
+
+For Azure Diagnostics tables, all data is written into one single table. Users specify which category they want to query. If you want to view the full-text query of your request, see [Monitor Azure Cosmos DB data by using diagnostic settings in Azure](../monitor-resource-logs.md#enable-full-text-query-for-logging-query-text) to learn how to enable this feature.
+
+For [resource-specific tables](../monitor-resource-logs.md#create-diagnostic-settings), data is written into individual tables for each category of the resource. We recommend this mode because it:
+
+- Makes it much easier to work with the data.
+- Provides better discoverability of the schemas.
+- Improves performance across both ingestion latency and query times.

articles/cosmos-db/includes/diagnostics-tables.md

@@ -302,7 +302,7 @@
               href: connect-using-mongochef.md
             - name: Connect using Compass
               href: connect-using-compass.md
-            - name: Connect using Robo 3T
+            - name: Connect using Studio 3T
               href: connect-using-robomongo.md
             - name: Connect using Mongoose
               href: connect-using-mongoose.md
@@ -425,8 +425,6 @@
           href: error-codes-solutions.md
         - name: Troubleshoot query performance
           href: troubleshoot-query-performance.md
-        - name: Troubleshoot API for MongoDB queries with diagnostics
-          href: diagnostic-queries.md
         - name: Prevent rate-limiting errors
           href: prevent-rate-limiting-errors.md
         - name: Optimize query and storage costs when upgrading
@@ -520,10 +518,10 @@
               href: ../monitor-resource-logs.md
             - name: Troubleshoot issues using basic queries
               href: ../monitor-logs-basic-queries.md
-            - name: Troubleshoot issues using advanced queries
-              href: ../advanced-queries.md
             - name: Audit control plane logs
               href: ../audit-control-plane-logs.md
+            - name: Troubleshoot issues with advanced diagnostics queries
+              href: diagnostic-queries.md
         - name: Configure alerts
           items:
             - name: Create alert on metrics