Skip to content

Commit 1d1feb6

Browse files
authored
[DOCS] Migrate search profile API examples (#126347)
1 parent 67fca83 commit 1d1feb6

File tree

4 files changed

+1084
-2
lines changed

4 files changed

+1084
-2
lines changed

docs/reference/elasticsearch/index-settings/slow-log.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,7 @@ If you aren’t sure how to start investigating traffic issues, consider enablin
216216

217217
Slow log thresholds being met does not guarantee cluster performance issues. In the event that symptoms are noticed, slow logs can provide helpful data to diagnose upstream traffic patterns or sources to resolve client-side issues. For example, you can use data included in `X-Opaque-ID`, the `_source` request body, or `user.*` fields to identify the source of your issue. This is similar to troubleshooting [live expensive tasks](docs-content://troubleshoot/elasticsearch/task-queue-backlog.md).
218218

219-
If you’re experiencing search performance issues, then you might also consider investigating searches flagged for their query durations using the [profile API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html). You can then use the profiled query to investigate optimization options using the [query profiler](docs-content://explore-analyze/query-filter/tools/search-profiler.md). This type of investigation should usually take place in a non-production environment.
219+
If you’re experiencing search performance issues, then you might also consider investigating searches flagged for their query durations using the [profile API](/reference/elasticsearch/rest-apis/search-profile.md). You can then use the profiled query to investigate optimization options using the [query profiler](docs-content://explore-analyze/query-filter/tools/search-profiler.md). This type of investigation should usually take place in a non-production environment.
220220

221221
Slow logging checks each event against the reporting threshold when the event is complete. This means that it can’t report if events trigger [circuit breaker errors](docs-content://troubleshoot/elasticsearch/circuit-breaker-errors.md). If suspect circuit breaker errors, then you should also consider enabling [audit logging](docs-content://deploy-manage/security/logging-configuration/enabling-audit-logs.md), which logs events before they are executed.
222222

docs/reference/elasticsearch/rest-apis/reciprocal-rank-fusion.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ The `rrf` retriever supports:
108108
* [suggesters](/reference/elasticsearch/rest-apis/search-suggesters.md)
109109
* [highlighting](/reference/elasticsearch/rest-apis/highlighting.md)
110110
* [collapse](/reference/elasticsearch/rest-apis/collapse-search-results.md)
111-
* [profiling](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html#profiling-queries)
111+
* [profiling](/reference/elasticsearch/rest-apis/search-profile.md)
112112

113113
The `rrf` retriever does not currently support:
114114

0 commit comments

Comments
 (0)