Merge pull request #6487 from HeidiSteen/heidist-freshness

JamesJBarnett · web-flow · commit e7ad9350b875 · 2025-08-08T14:26:03.000-07:00
Refreshed a few monitoring docs and renamed a file
diff --git a/articles/search/.openpublishing.redirection.search.json b/articles/search/.openpublishing.redirection.search.json
@@ -5,6 +5,11 @@
             "redirect_url": "/azure/search/search-how-to-managed-identities",
             "redirect_document_id": true
         },
+        {
+            "source_path_from_root": "/articles/search/search-howto-monitor-indexers.md",
+            "redirect_url": "/azure/search/search-monitor-indexers",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/search/cognitive-search-incremental-indexing-conceptual.md",
             "redirect_url": "/azure/search/enrichment-cache-how-to-manage",
diff --git a/articles/search/knowledge-store-projections-examples.md b/articles/search/knowledge-store-projections-examples.md
@@ -269,7 +269,7 @@ You can process projections by following these steps:
 
 1. [Run the indexer](/rest/api/searchservice/indexers/run) to put the skillset into execution. 
 
-1. [Monitor indexer execution](search-howto-monitor-indexers.md) to check progress and catch any errors.
+1. [Monitor indexer execution](search-monitor-indexers.md) to check progress and catch any errors.
 
 1. Use Azure portal to verify object creation in Azure Storage.
 
diff --git a/articles/search/media/search-monitor-indexers/indexers-list.png b/articles/search/media/search-monitor-indexers/indexers-list.png
diff --git a/articles/search/media/search-monitor-usage/monitoring-tab.png b/articles/search/media/search-monitor-usage/monitoring-tab.png
diff --git a/articles/search/monitor-azure-cognitive-search.md b/articles/search/monitor-azure-cognitive-search.md
@@ -13,9 +13,6 @@ ms.service: azure-ai-search
 
 [!INCLUDE [horz-monitor-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-intro.md)]
 
-> [!NOTE]
-> Azure AI Search doesn't log the identity of the person or app accessing content or operations on the search service. If you require this level of monitoring, you need to implement it in your client application.
-
 [!INCLUDE [horz-monitor-resource-types](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-types.md)]
 
 For more information about the resource types for Azure AI Search, see [Azure AI Search monitoring data reference](monitor-azure-cognitive-search-data-reference.md).
@@ -69,27 +66,6 @@ AzureDiagnostics
 | summarize count() by OperationName
 ```
 
-#### Long-running queries
-
-This Kusto query against AzureDiagnostics returns `Query.Search` operations, sorted by duration (in milliseconds). For more examples of `Query.Search` queries, see [Analyze performance in Azure AI Search](search-performance-analysis.md).
-
-```Kusto
-AzureDiagnostics
-| project OperationName, resultSignature_d, DurationMs, Query_s, Documents_d, IndexName_s
-| where OperationName == "Query.Search"
-| sort by DurationMs   
-```
-
-#### Indexer status
-
-This Kusto query returns the status of indexer operations. Results include the operation name, description of the request (which includes the name of the indexer), result status (Success or Failure), and the [HTTP status code](/rest/api/searchservice/http-status-codes). For more information about indexer execution, see [Monitor indexer status](search-howto-monitor-indexers.md).
-
-```Kusto
-AzureDiagnostics
-| project OperationName, Description_s, Documents_d, ResultType, resultSignature_d
-| where OperationName == "Indexers.Status"
-```
-
 [!INCLUDE [horz-monitor-alerts](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-alerts.md)]
 
 ### Azure AI Search alert rules
@@ -109,7 +85,7 @@ The following table lists common and recommended alert rules for Azure AI Search
 - [Azure AI Search monitoring data reference](monitor-azure-cognitive-search-data-reference.md)
 - [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource)
 - [Monitor queries](search-monitor-queries.md)
-- [Monitor indexer-based indexing](search-howto-monitor-indexers.md)
+- [Monitor indexer-based indexing](search-monitor-indexers.md)
 - [Visualize resource logs](search-monitor-logs-powerbi.md)
 - [Analyze performance in Azure AI Search](search-performance-analysis.md)
 - [Tips for better performance](search-performance-tips.md)
diff --git a/articles/search/search-file-storage-integration.md b/articles/search/search-file-storage-integration.md
@@ -228,7 +228,7 @@ Execution history contains up to 50 of the most recently completed executions, w
 
 ## Next steps
 
-You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-howto-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
+You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
 
 + [Change detection and deletion detection](search-howto-index-changed-deleted-blobs.md)
 + [Index large data sets](search-howto-large-index.md)
diff --git a/articles/search/search-how-to-create-indexers.md b/articles/search/search-how-to-create-indexers.md
@@ -231,7 +231,7 @@ Indexers are one of the few subsystems that make overt outbound calls to other A
 
 ## Check results
 
-[Monitor indexer status](search-howto-monitor-indexers.md) to check for status. Successful execution can still include warning and notifications. Be sure to check both successful and failed status notifications for details about the job.
+[Monitor indexer status](search-monitor-indexers.md) to check for status. Successful execution can still include warning and notifications. Be sure to check both successful and failed status notifications for details about the job.
 
 For content verification, [run queries](search-query-create.md) on the populated index that return entire documents or selected fields.
 
diff --git a/articles/search/search-how-to-index-onelake-files.md b/articles/search/search-how-to-index-onelake-files.md
@@ -420,7 +420,7 @@ By default, an indexer runs automatically when you create it. You can change thi
 
 ## Check indexer status
  
-Learn multiple approaches to [monitor the indexer status and execution history here](search-howto-monitor-indexers.md).
+Learn multiple approaches to [monitor the indexer status and execution history here](search-monitor-indexers.md).
 
 ## Handle errors
  
diff --git a/articles/search/search-how-to-large-index.md b/articles/search/search-how-to-large-index.md
@@ -139,4 +139,4 @@ If you have a big data architecture and your data is on a Spark cluster, we reco
 + [Tips for better performance in Azure AI Search](search-performance-tips.md)
 + [Analyze performance in Azure AI Search](search-performance-analysis.md)
 + [Indexers in Azure AI Search](search-indexer-overview.md)
-+ [Monitor indexer status and results in Azure AI Search](search-howto-monitor-indexers.md)
++ [Monitor indexer status and results in Azure AI Search](search-monitor-indexers.md)
diff --git a/articles/search/search-howto-index-azure-data-lake-storage.md b/articles/search/search-howto-index-azure-data-lake-storage.md
@@ -313,7 +313,7 @@ PUT /indexers/[indexer name]?api-version=2024-07-01
 
 ## Next steps
 
-You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-howto-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
+You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
 
 + [Change detection and deletion detection](search-howto-index-changed-deleted-blobs.md)
 + [Index large data sets](search-howto-large-index.md)
diff --git a/articles/search/search-howto-index-cosmosdb-mongodb.md b/articles/search/search-howto-index-cosmosdb-mongodb.md
@@ -304,7 +304,7 @@ api-key: [Search service admin key]
 
 ## Next steps
 
-You can now control how you [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-howto-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Cosmos DB:
+You can now control how you [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Cosmos DB:
 
 + [Set up an indexer connection to an Azure Cosmos DB database using a managed identity](search-howto-managed-identities-cosmos-db.md)
 + [Index large data sets](search-howto-large-index.md)
diff --git a/articles/search/search-howto-index-cosmosdb.md b/articles/search/search-howto-index-cosmosdb.md
@@ -460,7 +460,7 @@ For data accessed through the SQL API protocol, you can use the .NET SDK to auto
 
 ## Next steps
 
-You can now control how you [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-howto-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Cosmos DB:
+You can now control how you [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Cosmos DB:
 
 + [Set up an indexer connection to an Azure Cosmos DB database using a managed identity](search-howto-managed-identities-cosmos-db.md)
 + [Index large data sets](search-howto-large-index.md)
diff --git a/articles/search/search-howto-index-mysql.md b/articles/search/search-howto-index-mysql.md
@@ -263,7 +263,7 @@ The `softDeleteMarkerValue` must be a string. For example, if you have an intege
 
 ## Next steps
 
-You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-howto-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure MySQL:
+You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure MySQL:
 
 - [Index large data sets](search-howto-large-index.md)
 - [Indexer access to content protected by Azure network security features](search-indexer-securing-resources.md)
diff --git a/articles/search/search-howto-indexing-azure-tables.md b/articles/search/search-howto-indexing-azure-tables.md
@@ -308,7 +308,7 @@ Execution history contains up to 50 of the most recently completed executions, w
 
 ## Next steps
 
-Learn more about how to [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-howto-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
+Learn more about how to [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
 
 + [Tutorial: Index JSON blobs from Azure Storage](search-semi-structured-data.md)
 + [Tutorial: Index encrypted blobs in Azure Storage](search-howto-index-encrypted-blobs.md)
diff --git a/articles/search/search-howto-run-reset-indexers.md b/articles/search/search-howto-run-reset-indexers.md
@@ -330,6 +330,6 @@ Reset APIs are used to inform the scope of the next indexer run. For actual proc
 
 After you reset and rerun indexer jobs, you can monitor status from the search service, or obtain detailed information through resource logging.
 
-+ [Monitor search indexer status](search-howto-monitor-indexers.md)
++ [Monitor search indexer status](search-monitor-indexers.md)
 + [Collect and analyze log data](monitor-azure-cognitive-search.md)
 + [Schedule an indexer](search-howto-schedule-indexers.md)
diff --git a/articles/search/search-howto-schedule-indexers.md b/articles/search/search-howto-schedule-indexers.md
@@ -138,6 +138,6 @@ If an indexer is set to a certain schedule but repeatedly fails on the same docu
 
 For indexers that run on a schedule, you can monitor operations by retrieving status from the search service, or obtain detailed information by enabling resource logging.
 
-+ [Monitor search indexer status](search-howto-monitor-indexers.md)
++ [Monitor search indexer status](search-monitor-indexers.md)
 + [Collect and analyze log data](monitor-azure-cognitive-search.md)
 + [Index large data sets](search-howto-large-index.md)
diff --git a/articles/search/search-indexer-overview.md b/articles/search/search-indexer-overview.md
@@ -151,7 +151,7 @@ For more information, see [Create an indexer](search-howto-create-indexers.md)
 
 After the first indexer run, you can [rerun it on demand](search-howto-run-reset-indexers.md) or [set up a schedule](search-howto-schedule-indexers.md).
 
-You can monitor [indexer status in the Azure portal](search-howto-monitor-indexers.md) or through [Get Indexer Status API](/rest/api/searchservice/indexers/get-status). You should also [run queries on the index](search-query-create.md) to verify the result is what you expected.
+You can monitor [indexer status in the Azure portal](search-monitor-indexers.md) or through [Get Indexer Status API](/rest/api/searchservice/indexers/get-status). You should also [run queries on the index](search-query-create.md) to verify the result is what you expected.
 
 Indexers don't have dedicated processing resources. Based on this, indexers' status may show as idle before running (depending on other jobs in the queue) and run times may not be predictable. Other factors define indexer performance as well, such as document size, document complexity, image analysis, among others.
 
@@ -163,4 +163,4 @@ Now that you've been introduced to indexers, a next step is to review indexer pr
 + [Reset and run indexers](search-howto-run-reset-indexers.md)
 + [Schedule indexers](search-howto-schedule-indexers.md)
 + [Define field mappings](search-indexer-field-mappings.md)
-+ [Monitor indexer status](search-howto-monitor-indexers.md)
++ [Monitor indexer status](search-monitor-indexers.md)
diff --git a/articles/search/search-indexer-troubleshooting.md b/articles/search/search-indexer-troubleshooting.md
@@ -289,4 +289,4 @@ If you have [sensitivity labels set on documents](/microsoft-365/compliance/sens
 ## See also
 
 * [Troubleshooting common indexer errors and warnings](cognitive-search-common-errors-warnings.md)
-* [Monitor indexer-based indexing](search-howto-monitor-indexers.md)
+* [Monitor indexer-based indexing](search-monitor-indexers.md)
diff --git a/articles/search/search-monitor-enable-logging.md b/articles/search/search-monitor-enable-logging.md
@@ -7,28 +7,29 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: azure-ai-search
 ms.topic: how-to
-ms.date: 07/25/2025
+ms.date: 08/08/2025
 ---
 
 # Configure diagnostic logging for Azure AI Search
 
-Resource-level diagnostic logs provide insight into operations that occur in your Azure AI Search resource. In contrast, activity logs provide an insight into the operations performed on each Azure resource in the subscription from the outside, known as the [control plane](/azure/azure-resource-manager/management/control-plane-and-data-plane). Activity logging is enabled automatically, and often
+Diagnostic logs provide insight into operations that occur in your Azure AI Search resource. In contrast to Activity Logs that track operations performed on Azure resources at the subscription level, known as the [control plane](/azure/azure-resource-manager/management/control-plane-and-data-plane), diagnostic logging monitors operations on the search service itself. Diagnostic logging is essential for effective oversight of service operations like indexing and queries.
 
-This article explains how to enable resource-level diagnostic logging and how to find information about system and user operations on an Azure AI Search resource.
+This article explains how to enable diagnostic logging and find information about system and user operations on an Azure AI Search resource.
+
+> [!NOTE]
+> Azure AI Search doesn't log the identity of the person or app accessing content or operations on the search service. If you require this level of monitoring, you need to implement it in your client application.
 
 ## Prerequisites
 
 - An [Azure Log Analytics workspace](/azure/azure-monitor/logs/quick-create-workspace) in the same subscription.
 
 ## Enable diagnostic logging
 
-Diagnostic logging is available through Azure Monitor. Although some logging, like Activity Logs and built-in metrics, is reported automatically with no upfront configuration, resource-level logs about in-service operations and data access require that you create a diagnostic setting and specify a storage option.
-
-1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your search service.
+1. Sign in to the [Azure portal](https://portal.azure.com) and [find your search service](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices).
 
 1. Under **Monitoring** > **Diagnostic settings**, select **Add diagnostic setting**.
 
-1. Provide a name that identifies the service and level of logging, such as "my-search-service-all-logs" or "my-search-service-audit-logs".
+1. Provide a descriptive name that identifies the service and level of logging, such as "my-search-service-all-logs" or "my-search-service-audit-logs".
 
 1. Under **Logs**, choose a category:
 
@@ -38,20 +39,20 @@ Diagnostic logging is available through Azure Monitor. Although some logging, li
 
    Verbose logging can be expensive to store and complex to manage and store. You might want to start with **allLogs** and then switch to more scoped logging if it meets your information requirements. For more information about these categories, see [Diagnostic settings in Azure Monitor](/azure/azure-monitor/essentials/diagnostic-settings).
 
-1. For a destination, we recommend **Send to Log Analytics workspace** so that you can run Kusto queries against the data. There should be a workspace available
+1. For a destination, we recommend **Send to Log Analytics workspace** so that you can run Kusto queries against the data. Provide an existing Log Analytics workspace to store your logs.
 
 1. Save the settings.
 
 Repeat these steps if you require a more [comprehensive data collection strategy](/azure/azure-monitor/logs/workspace-design). 
 
-Each diagnostic setting you create requires its own data sink. If you use the Azure portal to review logs, the first diagnostic setting is used by default. You can navigate to specific workspaces for visualization support.
+Each diagnostic setting you create requires separate storage. If you use the Azure portal to review logs, the first diagnostic setting is used by default. You can navigate to specific workspaces for visualization support.
 
 > [!NOTE]
 > If you're using [key-based authentication](search-security-api-keys.md), Azure AI Search can't monitor individual user access to content on the search service. If you require this level of monitoring, you need to implement it in your client application.
 
 ## View logs in Log Analytics
 
-Follow these instructions to explore log analytics data for your resource.
+Follow these instructions to explore log analytics data for your search service.
 
 1. Under **Monitoring**, select **Logs**. Query hub opens by default. You can try the available queries, or close the hub and open a query window in KQL mode to run queries written in the [Kusto Query Language (KQL)](/kusto/query).
 
@@ -61,7 +62,7 @@ Follow these instructions to explore log analytics data for your resource.
 
    :::image type="content" source="media/search-monitor-enable-logging/query-example.png" alt-text="Screenshot of a query and results in the Azure portal.":::
 
-### Sample queries
+## Sample Kusto queries
 
 Here are a few basic Kusto queries you can use to explore your log data.
 
diff --git a/articles/search/search-monitor-indexers.md b/articles/search/search-monitor-indexers.md
diff --git a/articles/search/search-monitor-queries.md b/articles/search/search-monitor-queries.md
diff --git a/articles/search/toc.yml b/articles/search/toc.yml
