Fix links to profile API (elastic#1032)

Author: lcawl

deploy-manage/production-guidance/optimize-performance/search-speed.md

@@ -365,7 +365,7 @@ So what is the right number of replicas? If you have a cluster that has `num_nod
 
 ## Tune your queries with the Search Profiler [_tune_your_queries_with_the_search_profiler]
 
-The [Profile API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html) provides detailed information about how each component of your queries and aggregations impacts the time it takes to process the request.
+The [Profile API](elasticsearch://reference/elasticsearch/rest-apis/search-profile.md) provides detailed information about how each component of your queries and aggregations impacts the time it takes to process the request.
 
 The [Search Profiler](../../../explore-analyze/query-filter/tools/search-profiler.md) in {{kib}} makes it easy to navigate and analyze the profile results and give you insight into how to tune your queries to improve performance and reduce load.
 

explore-analyze/query-filter/tools/search-profiler.md

@@ -9,7 +9,7 @@ mapped_pages:
 
 # Search profiler [xpack-profiler]
 
-{{es}} has a powerful [Profile API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html) that you can use to inspect and analyze your search queries. The response returns a large JSON blob, which can be difficult to analyze manually.
+{{es}} has a powerful [Profile API](elasticsearch://reference/elasticsearch/rest-apis/search-profile.md) that you can use to inspect and analyze your search queries. The response returns a large JSON blob, which can be difficult to analyze manually.
 
 The **{{searchprofiler}}** tool can transform this JSON output into a visualization that is easy to navigate, allowing you to diagnose and debug poorly performing queries much faster.
 
@@ -35,7 +35,7 @@ While the cumulative time metric is useful for comparing the performance of your
 ::::
 
 
-To see more profiling information, click **View details**. You’ll see details about the query components that ran on the shard and the timing breakdown of low-level methods. For more information, refer to [Profiling queries](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html#profiling-queries).
+To see more profiling information, click **View details**. You’ll see details about the query components that ran on the shard and the timing breakdown of low-level methods. For more information, refer to [Profiling queries](elasticsearch://reference/elasticsearch/rest-apis/search-profile.md#profiling-queries).
 
 
 ## Filter for an index or type [_filter_for_an_index_or_type]
@@ -130,7 +130,7 @@ To understand how the query trees are displayed inside the **{{searchprofiler}}*
     :screenshot:
     :::
 
-    For more information about how the **{{searchprofiler}}** works, how timings are calculated, and how to interpret various results, see [Profiling queries](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html#profiling-queries).
+    For more information about how the **{{searchprofiler}}** works, how timings are calculated, and how to interpret various results, see [Profiling queries](elasticsearch://reference/elasticsearch/rest-apis/search-profile.md#profiling-queries).
 
 
 

explore-analyze/transforms/transform-scale.md

@@ -45,7 +45,7 @@ Use the [Preview {{transform}}](https://www.elastic.co/docs/api/doc/elasticsearc
 
 ## 3. Profile and optimize your search queries (search) [search-queries]
 
-If you have defined a {{transform}} source index `query`, ensure it is as efficient as possible. Use the **Search Profiler** under **Dev Tools** in {{kib}} to get detailed timing information about the execution of individual components in the search request. Alternatively, you can use the [Profile](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html). The results give you insight into how search requests are executed at a low level so that you can understand why certain requests are slow, and take steps to improve them.
+If you have defined a {{transform}} source index `query`, ensure it is as efficient as possible. Use the **Search Profiler** under **Dev Tools** in {{kib}} to get detailed timing information about the execution of individual components in the search request. Alternatively, you can use the [Profile](elasticsearch://reference/elasticsearch/rest-apis/search-profile.md). The results give you insight into how search requests are executed at a low level so that you can understand why certain requests are slow, and take steps to improve them.
 
 {{transforms-cap}} execute standard {{es}} search requests. There are different ways to write {{es}} queries, and some of them are more efficient than others. Consult [*Tune for search speed*](../../deploy-manage/production-guidance/optimize-performance/search-speed.md) to learn more about {{es}} performance tuning.
 

troubleshoot/elasticsearch/troubleshooting-searches.md

@@ -209,7 +209,7 @@ GET /my-index-000001/_explain/0
 }
 ```
 
-The [profile API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html) provides detailed timing information about a search request. For a visual representation of the results, use the [Search Profiler](../../explore-analyze/query-filter/tools/search-profiler.md) in {{kib}}.
+The [profile API](elasticsearch://reference/elasticsearch/rest-apis/search-profile.md) provides detailed timing information about a search request. For a visual representation of the results, use the [Search Profiler](../../explore-analyze/query-filter/tools/search-profiler.md) in {{kib}}.
 
 ::::{note}
 To troubleshoot queries in {{kib}}, select **Inspect** in the toolbar. Next, select **Request**. You can now copy the query {{kib}} sent to {{es}} for further analysis in Console.