Merge pull request #203944 from HeidiSteen/heidist-fresh

[azure search] Monitoring, REST APIs

Author: PRMerger16

articles/search/monitor-azure-cognitive-search.md

@@ -13,22 +13,33 @@ ms.custom: subject-monitoring
 
 # Monitoring Azure Cognitive Search
 
-When you have critical applications and business processes relying on Azure resources, you want to monitor those resources for their availability, performance, and operation. This article describes the monitoring data generated by Azure Cognitive Search and how to analyze and alert on this data with Azure Monitor.
+This article describes the metrics and usage data collected by Azure Cognitive Search. While these metrics are helpful, you can also expand the scope and durability of monitoring and data collection through Azure Monitor.
 
-## Performance and usage data in Azure portal
+## Monitoring in Azure portal
 
-In Azure portal, the search service **Overview** page includes a **Monitoring** tab that summarizes key metrics, including query volume, latency, and throttled queries. This data is collected automatically and stored internally for up to 30 days. Data becomes available for analysis as soon as you create the resource.
+In the search services pages in Azure portal, you can find current status of service operations and resource availability.
 
   ![Azure Monitor integration in a search service](./media/search-monitor-usage/azure-monitor-search.png "Azure Monitor integration in a search service")
 
-Azure portal pages also include a standard **Activity log** page that reports on search activity at the subscription level. Service administration and control plane operations are reflected in the log.
+On the **Overview** page, the **Monitoring** tab summarizes key [query metrics](search-monitor-queries.md), including query volume, latency, and throttled queries. This data is collected automatically and stored internally for up to 30 days. Data becomes available for analysis as soon as you create the resource.
 
-The **Usage** tab reports on available capacity and the quantity of indexes, indexers, data sources, and skillsets relative to the maximum allowed for your [service tier](search-sku-tier.md).
+On the **Overview** page, the **Usage** tab reports on available capacity and the quantity of indexes, indexers, data sources, and skillsets relative to the maximum allowed for your [service tier](search-sku-tier.md).
+
+From the menu on the left, open the standard **Activity log** page to view search activity at the subscription level. Service administration and control plane operations through Azure Resource Manager are reflected in the activity log.
 
 > [!NOTE]
 > Cognitive Search does not monitor individual user access to search data (sometimes referred to as document-level or row-level access). Indexing and query requests originate from a client application that presents either an admin or query API key on the request.
 
-While these metrics are helpful, you might want to expand the scope and durability of monitoring and data collection. Additional data collection is supported through Azure Monitor.
+## Get system data from REST APIs
+
+Although query metrics aren't available through REST, the **Usage** data that's visible in the portal can be obtained programmatically:
+
+* [Service Statistics (REST)](/rest/api/searchservice/get-service-statistics)
+* [Index Statistics (REST)](/rest/api/searchservice/get-index-statistics)
+* [Document Counts (REST)](/rest/api/searchservice/count-documents)
+* [Indexer Status (REST)](/rest/api/searchservice/get-indexer-status)
+
+For REST calls, use an [admin API key](search-security-api-keys.md) and [Postman](search-get-started-rest.md) or another REST client to query your search service.
 
 ## Expand monitoring with Azure Monitor
 
@@ -46,15 +57,6 @@ The following sections build on this article by describing the specific data gat
 
 Azure Cognitive Search collects the same kinds of monitoring data as other Azure resources that are described in [Monitoring data from Azure resources](../azure-monitor/essentials/monitor-azure-resource.md). See the [data reference](monitor-azure-cognitive-search-data-reference.md) for detailed information on the metrics and logs metrics created by Azure Cognitive Search.
 
-In addition to the resource logs collected by Azure Monitor, you can also obtain system data from the search service itself, including statistics, counts, and status:
-
-* [Service Statistics (REST)](/rest/api/searchservice/get-service-statistics)
-* [Index Statistics (REST)](/rest/api/searchservice/get-index-statistics)
-* [Document Counts (REST)](/rest/api/searchservice/count-documents)
-* [Indexer Status (REST)](/rest/api/searchservice/get-indexer-status)
-
-The system information above information can also be read from the Azure portal. For REST calls, use an [admin API key](search-security-api-keys.md) and [Postman](search-get-started-rest.md) or another REST client.
-
 ## Collection and routing
 
 Platform metrics and the Activity log are collected and stored automatically, but can be routed to other locations by using a diagnostic setting.