fix links

Author: colleenmcginnis

solutions/observability/apps/apm-ui-api.md

@@ -61,7 +61,7 @@ curl -X POST \
 
 ## Kibana API [kibana-api] 
 
-In addition to the APM specific API endpoints, Kibana provides its own [REST API](https://www.elastic.co/guide/en/observability/current/api.html) which you can use to automate certain aspects of configuring and deploying Kibana.
+In addition to the APM specific API endpoints, Kibana provides its own [REST API](https://www.elastic.co/guide/en/observability/current/apm-api.html) which you can use to automate certain aspects of configuring and deploying Kibana.
 
 
 

solutions/observability/apps/cross-cluster-search-with-application-data.md

@@ -9,7 +9,7 @@ mapped_pages:
 # Cross-cluster search with application data [apm-cross-cluster-search]
 
 
-Elastic APM utilizes {{es}}'s cross-cluster search functionality. Cross-cluster search lets you run a single search request against one or more [remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-remote-clusters.html) — making it easy to search APM data across multiple sources. This means you can also have deployments per data type, making sizing and scaling more predictable, and allowing for better performance while managing multiple observability use cases.
+Elastic APM utilizes {{es}}'s cross-cluster search functionality. Cross-cluster search lets you run a single search request against one or more [remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/remote-clusters.html) — making it easy to search APM data across multiple sources. This means you can also have deployments per data type, making sizing and scaling more predictable, and allowing for better performance while managing multiple observability use cases.
 
 
 ## Set up cross-cluster search [apm-set-up-cross-cluster-search]
@@ -18,9 +18,9 @@ Elastic APM utilizes {{es}}'s cross-cluster search functionality. Cross-cluster
 
 If you’re using the Hosted {{ess}}, see [Enable cross-cluster search](../../../deploy-manage/remote-clusters/ec-enable-ccs.md).
 
-To add remote clusters directly in {{kib}}, find `Remote Clusters` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). All you need is a name for the remote cluster and the seed node(s). Remember the names of your remote clusters, you’ll need them in step two. See [managing remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/ccr-getting-started.html) for detailed information on the setup process.
+To add remote clusters directly in {{kib}}, find `Remote Clusters` in the [global search field](../../../get-started/the-stack.md#kibana-navigation-search). All you need is a name for the remote cluster and the seed node(s). Remember the names of your remote clusters, you’ll need them in step two. See [managing remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/ccr-getting-started-tutorial.html) for detailed information on the setup process.
 
-Alternatively, you can [configure remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-remote-clusters.html#configuring-remote-clusters) in {{es}}'s `elasticsearch.yml` file.
+Alternatively, you can [configure remote clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/remote-clusters.html#configuring-remote-clusters) in {{es}}'s `elasticsearch.yml` file.
 
 **Step 2. Edit the default Applications UI {{data-sources}}.**
 

solutions/observability/apps/explore-data-in-elasticsearch.md

@@ -14,7 +14,7 @@ Elastic APM data is stored in [Data streams](data-streams.md).
 
 The following examples enable you to interact with {{es}}'s REST API. One possible way to do this is using {{kib}}'s [{{dev-tools-app}} console](../../../explore-analyze/query-filter/tools/console.md).
 
-Data streams, templates, and index-level operations can also be manged via {{kib}}'s [Index management](https://www.elastic.co/guide/en/kibana/current/managing-indices.html) panel.
+Data streams, templates, and index-level operations can also be manged via {{kib}}'s [Index management](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-mgmt.html) panel.
 
 To see an overview of existing data streams, run:
 

solutions/observability/apps/inspect-uptime-duration-anomalies.md

@@ -16,7 +16,7 @@ Create a {{ml}} job to detect anomalous monitor duration rates automatically.
 2. In the **Monitor duration** panel, click **Enable anomaly detection**.
 
     ::::{note}
-    If {{anomaly-detect}} is already enabled, click **Anomaly detection** and select to view duration anomalies directly in the [{{ml-app}} app](https://www.elastic.co/guide/en/machine-learning/current/ml-gs-results.html), enable an [anomaly rule](../incident-management/create-an-uptime-duration-anomaly-rule.md), or disable the {{anomaly-detect}}.
+    If {{anomaly-detect}} is already enabled, click **Anomaly detection** and select to view duration anomalies directly in the [{{ml-app}} app](https://www.elastic.co/guide/en/machine-learning/current/ml-getting-started.html#sample-data-results), enable an [anomaly rule](../incident-management/create-an-uptime-duration-anomaly-rule.md), or disable the {{anomaly-detect}}.
 
     ::::
 

solutions/observability/apps/switch-self-installation-to-apm-integration.md

@@ -25,7 +25,7 @@ Review the APM [release notes](https://www.elastic.co/guide/en/observability/cur
 
 ## Add a {{fleet}} Server [apm-integration-upgrade-2]
 
-{{fleet}} Server is a component of the {{stack}} used to centrally manage {{agent}}s. The APM integration requires a {{fleet}} Server to be running and accessible to your hosts. Add a {{fleet}} Server by following [this guide](https://www.elastic.co/guide/en/fleet/current/add-a-fleet-server.html).
+{{fleet}} Server is a component of the {{stack}} used to centrally manage {{agent}}s. The APM integration requires a {{fleet}} Server to be running and accessible to your hosts. Add a {{fleet}} Server by following [this guide](https://www.elastic.co/guide/en/fleet/current/fleet-deployment-models.html).
 
 ::::{tip}
 If you’re upgrading a self-managed deployment of the {{stack}}, you’ll need to enable [{{es}} security](../../../deploy-manage/deploy/self-managed/installing-elasticsearch.md) and the [API key service](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settings.html).

solutions/observability/apps/view-monitor-status.md

@@ -63,5 +63,5 @@ Depending on the features you have installed and configured, you can view logs,
 
 * Show host, pod, or container logs in the [{{logs-app}}](../logs/explore-logs.md).
 * Show APM data in the [Applications UI](traces-2.md).
-* Show host, pod, or container metrics in the [{{infrastructure-app}}](https://www.elastic.co/guide/en/observability/current/analyze-metrics.html).
+* Show host, pod, or container metrics in the [{{infrastructure-app}}](https://www.elastic.co/guide/en/observability/current/monitor-infrastructure-and-hosts.html).
 

solutions/observability/infra-and-hosts/explore-infrastructure-metrics-over-time.md

@@ -7,7 +7,7 @@ mapped_pages:
 
 The **Metrics Explorer** page enables you to create time-series visualizations based on aggregation of your metrics, chart them against related metrics, and break them down per the field of your choice. You can group and create visualizations of metrics for one or more resources that you are monitoring.
 
-Additionally, for detailed analyses of your metrics, you can annotate and save visualizations for your custom dashboards by using the [Time Series Visual Builder (TSVB)](https://www.elastic.co/guide/en/kibana/current/tsvb.html) within {{kib}}.
+Additionally, for detailed analyses of your metrics, you can annotate and save visualizations for your custom dashboards by using the [Time Series Visual Builder (TSVB)](https://www.elastic.co/guide/en/kibana/current/legacy-editors.html#tsvb-panel) within {{kib}}.
 
 To open **Metrics Explorer**, find **Infrastructure** in the main menu or use the [global search field](../../../get-started/the-stack.md#kibana-navigation-search).
 
@@ -53,7 +53,7 @@ As an example, let’s view the system load metrics for hosts we’re currently
 
     There is now a separate graph for each network interface.
 
-7. Let’s visualize one of the graphs in [TSVB](https://www.elastic.co/guide/en/kibana/current/tsvb.html). Choose a graph, click **Actions**, and then select **Open In Visualize**.
+7. Let’s visualize one of the graphs in [TSVB](https://www.elastic.co/guide/en/kibana/current/legacy-editors.html#tsvb-panel). Choose a graph, click **Actions**, and then select **Open In Visualize**.
 
     In this visualization the max of `host.network.egress.bytes` is displayed, filtered by `host.name` and `system.network.name`.
 

solutions/observability/logs/inspect-log-anomalies.md

@@ -57,4 +57,4 @@ The level of anomaly detected in a time period is color-coded, from red, orange,
 
 To help you further drill down into a potential anomaly, you can view an anomaly chart for each partition. Anomaly scores range from 0 (no anomalies) to 100 (critical).
 
-To analyze the anomalies in more detail, click **View anomaly in {{ml}}**, which opens the [Anomaly Explorer in {{ml-app}}](https://www.elastic.co/guide/en/machine-learning/current/ml-gs-results.html).
+To analyze the anomalies in more detail, click **View anomaly in {{ml}}**, which opens the [Anomaly Explorer in {{ml-app}}](https://www.elastic.co/guide/en/machine-learning/current/ml-getting-started.html#sample-data-results).

solutions/observability/unknown-bucket/view-monitor-status.md

@@ -63,5 +63,5 @@ Depending on the features you have installed and configured, you can view logs,
 
 * Show host, pod, or container logs in the [{{logs-app}}](../logs/explore-logs.md).
 * Show APM data in the [Applications UI](../apps/traces-2.md).
-* Show host, pod, or container metrics in the [{{infrastructure-app}}](https://www.elastic.co/guide/en/observability/current/analyze-metrics.html).
+* Show host, pod, or container metrics in the [{{infrastructure-app}}](https://www.elastic.co/guide/en/observability/current/monitor-infrastructure-and-hosts.html).
 

solutions/search/elasticsearch-basics-quickstart.md

@@ -397,7 +397,7 @@ GET books/_search
 
 1. The `took` field indicates the time in milliseconds for {{es}} to execute the search
 2. The `timed_out` field indicates whether the search timed out
-3. The `_shards` field contains information about the number of [shards](https://www.elastic.co/guide/en/elasticsearch/reference/current/glossary.html) that the search was executed on and the number that succeeded
+3. The `_shards` field contains information about the number of [shards](https://www.elastic.co/guide/en/elastic-stack-glossary/current/terms.html) that the search was executed on and the number that succeeded
 4. The `hits` object contains the search results
 5. The `total` object provides information about the total number of matching documents
 6. The `max_score` field indicates the highest relevance score among all matching documents