Skip to content

Commit 2189547

Browse files
committed
fixed links
1 parent 3e548c6 commit 2189547

File tree

2 files changed

+0
-4
lines changed

2 files changed

+0
-4
lines changed

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

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,8 +109,6 @@ The following table lists common and recommended alert rules for Azure AI Search
109109
- [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource)
110110
- [Monitor queries](search-monitor-queries.md)
111111
- [Monitor indexer-based indexing](search-howto-monitor-indexers.md)
112-
- [Monitor client-side interactions](search-traffic-analytics.md)
113112
- [Visualize resource logs](search-monitor-logs-powerbi.md)
114113
- [Analyze performance in Azure AI Search](search-performance-analysis.md)
115-
- [Performance benchmarks](performance-benchmarks.md)
116114
- [Tips for better performance](search-performance-tips.md)

articles/search/search-performance-analysis.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ This article describes the tools, behaviors, and approaches for analyzing query
1717

1818
In any large implementation, it's critical to do a performance benchmarking test of your Azure AI Search service before you roll it into production. You should test both the search query load that you expect, but also the expected data ingestion workloads (if possible, run both workloads simultaneously). Having benchmark numbers helps to validate the proper [search tier](search-sku-tier.md), [service configuration](search-capacity-planning.md), and expected [query latency](search-performance-analysis.md#average-query-latency).
1919

20-
<!-- To develop benchmarks, we recommend the [azure-search-performance-testing (GitHub)](https://github.com/Azure-Samples/azure-search-performance-testing) tool. -->
21-
2220
To isolate the effects of a distributed service architecture, try testing on service configurations of one replica and one partition.
2321

2422
> [!NOTE]

0 commit comments

Comments
 (0)