Add missing redirects

_api-reference/analyze-apis.md

@@ -6,6 +6,7 @@ redirect_from:
   - /api-reference/analyze-apis/perform-text-analysis/
   - /opensearch/rest-api/analyze-apis/
   - /api-reference/analyze-apis/terminology/
+  - /api-reference/analyze-apis/index/
 ---
 
 # Analyze API

_api-reference/cluster-api/cluster-decommission.md

@@ -15,7 +15,7 @@ redirect_from:
 
 The cluster decommission operation adds support decommissioning based on awareness. It greatly benefits multi-zone deployments, where awareness attributes, such as `zones`, can aid in applying new upgrades to a cluster in a controlled fashion. This is especially useful during outages, in which case, you can decommission the unhealthy zone to prevent replication requests from stalling and prevent your request backlog from becoming too large.
 
-For more information about allocation awareness, see [Shard allocation awareness]({{site.url}}{{site.baseurl}}//opensearch/cluster/#shard-allocation-awareness).
+For more information about allocation awareness, see [Shard allocation awareness]({{site.url}}{{site.baseurl}}/opensearch/cluster/#shard-allocation-awareness).
 
 
 ## Endpoints

_api-reference/security/index.md

@@ -6,6 +6,7 @@ has_children: true
 redirect_from:
   - /api-reference/security-api/
   - /api-reference/security/
+  - /security-plugin/access-control/api/
 ---
 
 # Security APIs

_benchmark/reference/commands/index.md

@@ -7,6 +7,7 @@ parent: OpenSearch Benchmark Reference
 redirect_from:
   - /benchmark/commands/index/
   - /benchmark/reference/commands/
+  - /benchmark/commands/execute-test/
 ---
 
 # OpenSearch Benchmark command reference

_benchmark/user-guide/index.md

@@ -25,6 +25,9 @@ more_cards:
     link: "/benchmark/user-guide/optimizing-benchmarks/index/" 
 redirect_from:
   - /benchmark/user-guide/
+  - /benchmark/configuring-benchmark/
+  - /benchmark/creating-custom-workloads/
+  - /benchmark/installing-benchmark/
 ---
 
 # OpenSearch Benchmark User Guide

_dashboards/discover/index-discover.md

@@ -3,8 +3,6 @@ layout: default
 title: Analyzing data
 nav_order: 20
 has_children: true
-redirect_from: 
-  - /dashboards/discover/index-discover/
 ---
 
 # Analyzing data

_dashboards/management/advanced-settings.md

@@ -117,7 +117,7 @@ The following table describes the **Search** settings.
 Setting | Description
 :--- | :--- 
 `courier:batchSearches`  | Enables or disables how dashboard panels load. When disabled, panels load individually, and search requests end when the user navigates away or updates the query. When enabled, all panels load together when all data is loaded, and searches do not end. Default is `Off`.  |
-`courier:customRequestPreference`  | Specifies whether to use the [request preference]({{site.url}}{{site.baseurl}}//api-reference/popular-api/) with the `custom` setting. Default is `_local`.  |
+`courier:customRequestPreference`  | Specifies whether to use the [request preference]({{site.url}}{{site.baseurl}}/api-reference/popular-api/) with the `custom` setting. Default is `_local`.  |
 `courier:ignoreFilterIfFieldNotInIndex`  | Enables or disables support for dashboards that contain visualizations using different indexes. When disabled, all filters are applied to all visualizations. When enabled, visualization filters are ignored if the visualization's index does not contain the field being filtered. Default is `Off`.  |
 `courier:maxConcurrentShardRequests`  | Defines the maximum number of concurrent shard requests that OpenSearch Dashboards can initiate for `_msearch` requests. Set to `0` to disable the setting and to use the default value set by OpenSearch. Default is `0`.  |
 `courier:setRequestPreference`  | Defines which shards handle your search requests. Options include **Session ID**, **Custom**, and **None**. **Session ID** restricts operations so that all search requests run on the same shard and reuses shard caches across requests, which can improve performance. **Custom** is used to define your own preference. Use `courier:customRequestPreference` to customize your preference value. **None** means that no preference is set. This option can provide better performance because requests can be spread across all shard copies. However, results might be inconsistent because different shards might be in different refresh states. Default is `Session ID`.  |

_dashboards/quickstart.md

@@ -6,6 +6,7 @@ has_children: false
 redirect_from:
   - /dashboards/get-started/quickstart-dashboards/
   - /dashboards/quickstart-dashboards/
+  - /dashboards/browser-compatibility/
 ---
 
 # OpenSearch Dashboards quickstart guide

_data-prepper/pipelines/configuration/processors/csv.md

@@ -53,7 +53,7 @@ When run, the processor will parse the message. Although only two column names a
 ```
 ### Automatically detect column names
 
-The following configuration automatically detects the header of a CSV file ingested through an [`s3 source`]({{site.url}}{{site.baseurl}}//data-prepper/pipelines/configuration/sources/s3/):
+The following configuration automatically detects the header of a CSV file ingested through an [`s3 source`]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/sources/s3/):
 
 ```yaml
 csv-s3-pipeline:

_data-prepper/pipelines/configuration/processors/processors.md

@@ -7,6 +7,7 @@ nav_order: 35
 redirect_from:
   - /data-prepper/pipelines/configuration/processors/mutate-event/
   - /data-prepper/pipelines/configuration/processors/mutate-string/
+  - /data-prepper/pipelines/configuration/processors/
 ---
 
 # Processors

_data-prepper/pipelines/configuration/sources/sources.md

@@ -4,6 +4,8 @@ title: Sources
 parent: Pipelines
 has_children: true
 nav_order: 110
+redirect_from:
+  - /data-prepper/pipelines/configuration/sources/
 ---
 
 # Sources

_ingest-pipelines/create-ingest.md

@@ -5,6 +5,7 @@ nav_order: 10
 redirect_from:
   - /opensearch/rest-api/ingest-apis/create-update-ingest/
   - /api-reference/ingest-apis/create-ingest/
+  - /api-reference/ingest-apis/create-update-ingest/
 ---
 
 # Create pipeline

_migrate-or-upgrade/index.md

@@ -11,6 +11,8 @@ redirect_from:
   - /upgrade-to/index/
   - /upgrade-to/
   - /upgrade-to/upgrade-to/
+  - /install-and-configure/upgrade-opensearch/index/
+  - /upgrade-to/docker-upgrade-to/
 nav_exclude: true
 ---
 # Migrate or upgrade OpenSearch

_migrate-or-upgrade/rolling-upgrade/index.md

@@ -5,10 +5,11 @@ nav_order: 20
 has_toc: true
 permalink: /migrate-or-upgrade/rolling-upgrade/
 nav_exclude: false
-redirect_from: 
+redirect_from:
  - /upgrade-opensearch/
  - /rolling-upgrade/index/
  - /migrate-or-upgrade/rolling-upgrade/appendix/
+ - /install-and-configure/upgrade-opensearch/rolling-upgrade/
 ---
 
 # Rolling upgrade

_ml-commons-plugin/agents-tools/tools/index.md

@@ -8,6 +8,7 @@ nav_order: 20
 redirect_from: 
   - /ml-commons-plugin/extensibility/index/
   - /ml-commons-plugin/agents-tools/tools/
+  - /ml-commons-plugin/agents-tools/tools/cat-index-tool/
 ---
 
 # Tools

_search-plugins/sql/ppl/functions.md

@@ -7,6 +7,7 @@ nav_order: 2
 redirect_from:
   - /observability-plugin/ppl/commands/
   - /search-plugins/ppl/commands/
+  - /search-plugins/ppl/functions/
 ---
 
 # Commands

_security/configuration/disable-enable-security.md

@@ -4,8 +4,9 @@ title: Disabling and enabling the Security plugin
 parent: Configuration
 nav_order: 40
 has_toc: true
-redirect_from: 
+redirect_from:
  - /security-plugin/configuration/disable/
+ - /security/configuration/disable/
 ---
 
 # Disabling and enabling the Security plugin

_security/multi-tenancy/tenant-index.md

@@ -7,6 +7,7 @@ has_toc: false
 redirect_from:
   - /security/multi-tenancy/
   - /security-plugin/access-control/multi-tenancy/
+  - /security/access-control/multi-tenancy/
 ---
 
 # OpenSearch Dashboards multi-tenancy

_tuning-your-cluster/availability-and-recovery/remote-store/index.md

@@ -61,7 +61,7 @@ During the bootstrapping process, the remote-backed repositories listed in `open
 
 ## Related cluster settings
 
-You can use the following [cluster settings]({{site.url}}{{site.baseurl}}//api-reference/cluster-api/cluster-settings/) to tune how remote-backed clusters handle each workload.
+You can use the following [cluster settings]({{site.url}}{{site.baseurl}}/api-reference/cluster-api/cluster-settings/) to tune how remote-backed clusters handle each workload.
 
 | Field | Data type | Description |
 | :--- | :--- | :--- |

_tuning-your-cluster/availability-and-recovery/workload-management/workload-group-rules.md

@@ -10,7 +10,7 @@ redirect_from:
 
 # Workload group rules
 
-Workload group rules allow you to automatically assign workload group IDs to incoming queries. When a query matches the attributes specified in a rule, OpenSearch tags the query with the corresponding workload group ID. This eliminates the need for clients to manually include the workload group ID in each request. For more information about auto-tagging requests, see [Rule-based auto-tagging]({{site.url}}{{site.baseurl}}//tuning-your-cluster/availability-and-recovery/rule-based-autotagging/autotagging/).
+Workload group rules allow you to automatically assign workload group IDs to incoming queries. When a query matches the attributes specified in a rule, OpenSearch tags the query with the corresponding workload group ID. This eliminates the need for clients to manually include the workload group ID in each request. For more information about auto-tagging requests, see [Rule-based auto-tagging]({{site.url}}{{site.baseurl}}/tuning-your-cluster/availability-and-recovery/rule-based-autotagging/autotagging/).
 
 ## Creating a rule
 

_vector-search/api/index.md

@@ -7,6 +7,7 @@ has_toc: false
 redirect_from:
   - /vector-search/api/knn/
   - /vector-search/api/
+  - /search-plugins/knn/api/
 ---
 
 # Vector search API

_vector-search/api/knn.md

@@ -4,6 +4,8 @@ title: k-NN API
 parent: Vector search API
 nav_order: 10
 has_children: false
+redirect_from:
+  - /search-plugins/knn/jni-libraries/
 ---
 
 # k-NN API