added screenshot

Add page for migrating to Dashboards

.gitignore

@@ -3,3 +3,5 @@ _site
 .jekyll-metadata
 .DS_Store
 Gemfile.lock
+.idea
+.jekyll-cache

NOTICE

@@ -1 +1 @@
-Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+Copyright 2021 OpenSearch contributors.

README.md

@@ -34,7 +34,7 @@ If you encounter problems or have questions when contributing to the documentati
 
 After each commit to this repository, GitHub Pages automatically uses [Jekyll](https://jekyllrb.com) to rebuild the [website](https://docs-beta.opensearch.org). The whole process takes around 30 seconds.
 
-This repository contains many [Markdown](https://guides.github.com/features/mastering-markdown/) files in the `/docs` directory. Each Markdown file correlates with one page on the website. For example, the Markdown file for [this page](https://docs-beta.opensearch.org/docs/opensearch/) is [here](https://github.com/opensearch-project/documentation-website/blob/master/docs/opensearch/index.md).
+This repository contains many [Markdown](https://guides.github.com/features/mastering-markdown/) files in the `/docs` directory. Each Markdown file correlates with one page on the website.
 
 Using plain text on GitHub has many advantages:
 
@@ -273,4 +273,4 @@ This project is licensed under the Apache-2.0 License.
 
 ## Copyright
 
-Copyright Amazon.com, Inc. or its affiliates. All rights reserved.
+Copyright 2021 OpenSearch contributors.

_clients/agents-and-ingestion-tools/index.md

@@ -0,0 +1,66 @@
+---
+layout: default
+title: Agents and ingestion tools
+nav_order: 100
+has_children: false
+has_toc: false
+---
+
+# Agents and ingestion tools
+
+Historically, many multiple popular agents and ingestion tools have worked with Elasticsearch OSS, such as Beats, Logstash, Fluentd, FluentBit, and OpenTelemetry. OpenSearch aims to continue to support a broad set of agents and ingestion tools, but not all have been tested or have explicitly added OpenSearch compatibility.
+
+As an intermediate solution, we are adding a [version value](https://github.com/opensearch-project/OpenSearch/issues/693) to `opensearch.yml`. This change will let you set OpenSearch 1.x clusters to report version 7.10.2 (or any other arbitrary value). By reporting 7.10.2, the cluster will be able to connect with tools that check for a particular version number.
+
+For a longer term solution, we plan to create an OpenSearch output plugin for Logstash. This plugin *does not exist yet*, but we've included it in the compatibility matrices below based on its expected behavior.
+
+
+## Downloads
+
+These versions of Logstash and Beats offer the best compatibility with OpenSearch. For more information, see the [compatibility matrices](#compatibility-matrices).
+
+- [Logstash OSS 7.12.1](https://www.elastic.co/downloads/past-releases/logstash-oss-7-12-1)
+- [Filebeat OSS 7.12.1](https://www.elastic.co/downloads/past-releases/filebeat-oss-7-12-1)
+- [Metricbeat OSS 7.12.1](https://www.elastic.co/downloads/past-releases/metricbeat-oss-7-12-1)
+- [Packetbeat OSS 7.12.1](https://www.elastic.co/downloads/past-releases/packetbeat-oss-7-12-1)
+- [Heartbeat OSS 7.12.1](https://elastic.co/downloads/past-releases/heartbeat-oss-7-12-1)
+- [Winlogbeat OSS 7.12.1](https://www.elastic.co/downloads/past-releases/winlogbeat-oss-7-12-1)
+- [Auditbeat OSS 7.12.1](https://elastic.co/downloads/past-releases/auditbeat-oss-7-12-1)
+
+
+## Compatibility Matrices
+
+*Italicized* cells are untested, but indicate what a value theoretically should be based on existing information.
+
+
+### Compatibility Matrix for Logstash
+
+| | Logstash OSS 7.x to 7.11.x | Logstash OSS 7.12.x\* | Logstash 7.13.x without OpenSearch output plugin | Logstash 7.13.x with OpenSearch output plugin\*\* |
+| :---| :--- | :--- | :--- | :--- |
+| Elasticsearch OSS v7.x to v7.9.x | *Yes* | *Yes* | *No* | *Yes* |
+| Elasticsearch OSS v7.10.2 | *Yes* | *Yes* | *No* | *Yes* |
+| ODFE OSS v1.x to 1.12 | *Yes* | *Yes* | *No* | *Yes* |
+| ODFE 1.13 | *Yes* | *Yes* | *No* | *Yes* |
+| OpenSearch 1.0 | [Yes via version setting](https://github.com/opensearch-project/OpenSearch/issues/693) | [Yes via version setting](https://github.com/opensearch-project/OpenSearch/issues/693) | *No* | *Yes* |
+
+\* Most current compatible version with Elasticsearch OSS.
+
+\*\* Planning to build.
+
+
+### Compatibility Matrix for Beats
+
+| | Beats OSS 7.x to 7.11.x\*\* | Beats OSS 7.12.x\* | Beats 7.13.x |
+| :--- | :--- | :--- | :--- |
+| Elasticsearch OSS v7.x to v7.9.x | *Yes* | *Yes* | No |
+| Elasticsearch OSS v7.10.2 | *Yes* | *Yes* | No |
+| ODFE OSS v1.x to 1.12 | *Yes* | *Yes* | No |
+| ODFE 1.13 | *Yes* | *Yes* | No |
+| OpenSearch 1.0 | [Yes via version setting](https://github.com/opensearch-project/OpenSearch/issues/693) | [Yes via version setting](https://github.com/opensearch-project/OpenSearch/issues/693) | No |
+| Logstash OSS 7.x to 7.11.x | *Yes* | *Yes* | *Yes* |
+| Logstash OSS 7.12.x\* | *Yes* | *Yes* | *Yes* |
+| Logstash 7.13.x with OpenSearch output plugin | *Yes* | *Yes* | *Yes* |
+
+\* Most current compatible version with Elasticsearch OSS.
+
+\*\* Beats OSS includes all Apache 2.0 Beats agents (i.e. Filebeat, Metricbeat, Auditbeat, Heartbeat, Winlogbeat, Packetbeat).

_clients/cli.md

@@ -3,13 +3,16 @@ layout: default
 title: OpenSearch CLI
 nav_order: 52
 has_children: false
+redirect_from:
+  - /docs/odfe-cli/
+  - /docs/cli/
 ---
 
 # OpenSearch CLI
 
 The OpenSearch CLI command line interface (opensearch-cli) lets you manage your OpenSearch cluster from the command line and automate tasks.
 
-Currently, opensearch-cli supports the [Anomaly Detection](../ad/) and [k-NN](../knn/) plugins, along with arbitrary REST API paths. Among other things, you can use opensearch-cli to create and delete detectors, start and stop them, and check k-NN statistics.
+Currently, opensearch-cli supports the [Anomaly Detection]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/) and [k-NN]({{site.url}}{{site.baseurl}}/search-plugins/knn/) plugins, along with arbitrary REST API paths. Among other things, you can use opensearch-cli to create and delete detectors, start and stop them, and check k-NN statistics.
 
 Profiles let you easily access different clusters or sign requests with different credentials. opensearch-cli supports unauthenticated requests, HTTP basic signing, and IAM signing for Amazon Web Services.
 

_config.yml

@@ -1,26 +1,11 @@
-# Welcome to Jekyll!
-#
-# This config file is meant for settings that affect your whole blog, values
-# which you are expected to set up once and rarely edit after that. If you find
-# yourself editing this file very often, consider using Jekyll's data files
-# feature for the data you need to update frequently.
-#
-# For technical reasons, this file is *NOT* reloaded automatically when you use
-# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
-
-# Site settings
-# These are used to personalize your new site. If you look in the HTML files,
-# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
-# You can create any custom variable you would like, and they will be accessible
-# in the templates via {{ site.myvariable }}.
 title: OpenSearch documentation
 description: >- # this means to ignore newlines until "baseurl:"
   Documentation for OpenSearch, the Apache 2.0 search, analytics, and visualization suite with advanced security, alerting, SQL support, automated index management, deep performance analysis, and more.
 baseurl: "" # the subpath of your site, e.g. /blog
 url: "https://docs-beta.opensearch.org" # the base hostname & protocol for your site, e.g. http://example.com
-permalink: pretty
+permalink: /:path/
 
-opensearch_version: 1.0.0-beta1
+opensearch_version: 1.0.0-rc1
 opensearch_major_minor_version: 1.0
 
 # Build settings
@@ -39,6 +24,76 @@ aux_links:
     - "https://opensearch.org"
 color_scheme: opensearch
 
+# Define Jekyll collections
+collections:
+  # Define a collection named "tests", its documents reside in the "_tests" directory
+  upgrade-to:
+    permalink: /:collection/:path/
+    output: true
+  opensearch:
+    permalink: /:collection/:path/
+    output: true
+  dashboards:
+    permalink: /:collection/:path/
+    output: true
+  security-plugin:
+    permalink: /:collection/:path/
+    output: true
+  search-plugins:
+    permalink: /:collection/:path/
+    output: true
+  im-plugin:
+    permalink: /:collection/:path/
+    output: true
+  monitoring-plugins:
+    permalink: /:collection/:path/
+    output: true
+  clients:
+    permalink: /:collection/:path/
+    output: true
+  troubleshoot:
+    permalink: /:collection/:path/
+    output: true
+  external_links:
+    permalink: /:collection/:path/
+    output: true
+
+just_the_docs:
+  # Define the collections used in the theme
+  collections:
+    upgrade-to:
+      name: Upgrade to OpenSearch
+      # nav_exclude: true
+      nav_fold: true
+      # search_exclude: true
+    opensearch:
+      name: OpenSearch
+      nav_fold: true
+    dashboards:
+      name: OpenSearch Dashboards
+      nav_fold: true
+    security-plugin:
+      name: Security plugin
+      nav_fold: true
+    search-plugins:
+      name: Search plugins
+      nav_fold: true
+    im-plugin:
+      name: Index management plugin
+      nav_fold: true
+    monitoring-plugins:
+      name: Monitoring plugins
+      nav_fold: true
+    clients:
+      name: Clients and tools
+      nav_fold: true
+    troubleshoot:
+      name: Troubleshooting
+      nav_fold: true
+    external_links:
+      name: External links
+
+
 # Enable or disable the site search
 # Supports true (default) or false
 search_enabled: true

_dashboards/browser-compatibility.md

@@ -0,0 +1,17 @@
+---
+layout: default
+title: Browser compatibility
+parent: OpenSearch Dashboards
+nav_order: 3
+---
+
+# Browser compatibility
+
+OpenSearch Dashboards supports the following web browsers:
+
+- Chrome
+- Firefox
+- Safari
+- Edge (Chromium)
+
+Other Chromium-based browsers might work, as well. Internet Explorer and Microsoft Edge Legacy are **not** supported.

_dashboards/gantt.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Gantt charts
-parent: OpenSearch Dashboards
 nav_order: 10
 ---
 
@@ -21,6 +20,6 @@ To create a Gantt chart, perform the following steps:
 1. Choose **Panel settings** to adjust axis labels, time format, and colors.
 1. Choose **Update**.
 
-![Gantt Chart](../../images/gantt-chart.png)
+![Gantt Chart]({{site.url}}{{site.baseurl}}/images/gantt-chart.png)
 
 This Gantt chart displays the ID of each log on the y-axis. Each bar is a unique event that spans some amount of time. Hover over a bar to see the duration of that event.

_dashboards/index.md

@@ -1,9 +1,13 @@
 ---
 layout: default
-title: OpenSearch Dashboards
-nav_order: 11
-has_children: true
+title: About Dashboards
+nav_order: 1
+has_children: false
 has_toc: false
+redirect_from:
+  - /docs/opensearch-dashboards/
+  - /opensearch-dashboards/
+  - /dashboards/
 ---
 
 # OpenSearch Dashboards

_dashboards/install/docker.md

@@ -2,7 +2,6 @@
 layout: default
 title: Docker
 parent: Install OpenSearch Dashboards
-grand_parent: OpenSearch Dashboards
 nav_order: 1
 ---
 
@@ -12,13 +11,13 @@ You *can* start OpenSearch Dashboards using `docker run` after [creating a Docke
 
 1. Run `docker pull opensearchproject/opensearch-dashboards:{{site.opensearch_version}}`.
 
-1. Create a [`docker-compose.yml`](https://docs.docker.com/compose/compose-file/) file appropriate for your environment. A sample file that includes OpenSearch Dashboards is available on the OpenSearch [Docker installation page](../opensearch/docker/#sample-docker-compose-file).
+1. Create a [`docker-compose.yml`](https://docs.docker.com/compose/compose-file/) file appropriate for your environment. A sample file that includes OpenSearch Dashboards is available on the OpenSearch [Docker installation page]({{site.url}}{{site.baseurl}}/opensearch/install/docker#sample-docker-compose-file).
 
    Just like `opensearch.yml`, you can pass a custom `opensearch_dashboards.yml` to the container in the Docker Compose file.
    {: .tip }
 
 1. Run `docker-compose up`.
 
-   Wait for the containers to start. Then see the [OpenSearch Dashboards documentation](../../../opensearch-dashboards/).
+   Wait for the containers to start. Then see the [OpenSearch Dashboards documentation]({{site.url}}{{site.baseurl}}/).
 
 1. When finished, run `docker-compose down`.

_dashboards/install/index.md

@@ -2,8 +2,9 @@
 layout: default
 title: Install OpenSearch Dashboards
 nav_order: 1
-parent: OpenSearch Dashboards
 has_children: true
+redirect_from:
+  - /dashboards/install/
 ---
 
 # Install and configure OpenSearch Dashboards

_dashboards/install/plugins.md

@@ -2,7 +2,6 @@
 layout: default
 title: OpenSearch Dashboards plugins
 parent: Install OpenSearch Dashboards
-grand_parent: OpenSearch Dashboards
 nav_order: 50
 ---
 
@@ -29,11 +28,25 @@ If you don't want to use the all-in-one installation options, you can install th
     </tr>
   </thead>
   <tbody>
+  <tr>
+    <td>1.0.0-rc1</td>
+    <td>
+      <pre>alertingDashboards          1.0.0.0-rc1
+anomalyDetectionDashboards  1.0.0.0-rc1
+ganttChartDashboards        1.0.0.0-rc1
+indexManagementDashboards   1.0.0.0-rc1
+notebooksDashboards         1.0.0.0-rc1
+queryWorkbenchDashboards    1.0.0.0-rc1
+reportsDashboards           1.0.0.0-rc1
+securityDashboards          1.0.0.0-rc1
+traceAnalyticsDashboards    1.0.0.0-rc1
+</pre>
+    </td>
+  </tr>
   <tr>
     <td>1.0.0-beta1</td>
     <td>
-      <pre>
-alertingDashboards          1.0.0.0-beta1
+      <pre>alertingDashboards          1.0.0.0-beta1
 anomalyDetectionDashboards  1.0.0.0-beta1
 ganttChartDashboards        1.0.0.0-beta1
 indexManagementDashboards   1.0.0.0-beta1
@@ -52,14 +65,15 @@ traceAnalyticsDashboards    1.0.0.0-beta1
 ## Prerequisites
 
 - A compatible OpenSearch cluster
-- The corresponding OpenSearch plugins [installed on that cluster](../../install/plugins)
-- The corresponding version of [OpenSearch Dashboards](../) (e.g. OpenSearch Dashboards 1.0.0 works with OpenSearch 1.0.0)
+- The corresponding OpenSearch plugins [installed on that cluster]({{site.url}}{{site.baseurl}}/opensearch/install/plugins/)
+- The corresponding version of [OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/) (e.g. OpenSearch Dashboards 1.0.0 works with OpenSearch 1.0.0)
 
 
 ## Install
 
 Navigate to the OpenSearch Dashboards home directory (likely `/usr/share/opensearch-dashboards`) and run the install command for each plugin.
 
+{% comment %}
 
 #### Security OpenSearch Dashboards
 
@@ -146,6 +160,7 @@ sudo bin/opensearch-dashboards-plugin install https://d3g5vo6xdbdb9a.cloudfront.
 
 This plugin adds a new Gantt chart visualization.
 
+{% endcomment %}
 
 ## List installed plugins
 
@@ -164,6 +179,8 @@ To remove a plugin:
 sudo bin/opensearch-dashboards-plugin remove <plugin-name>
 ```
 
+Then remove all associated entries from `opensearch_dashboards.yml`.
+
 For certain plugins, you must also remove the "optimze" bundle. This is a sample command for the Anomaly Detection plugin:
 
 ```bash

_dashboards/install/tar.md

@@ -2,7 +2,6 @@
 layout: default
 title: Tarball
 parent: Install OpenSearch Dashboards
-grand_parent: OpenSearch Dashboards
 nav_order: 30
 ---
 
@@ -28,4 +27,4 @@ nav_order: 30
    ./bin/opensearch-dashboards
    ```
 
-1. See the [OpenSearch Dashboards documentation](../../opensearch-dashboards/).
+1. See the [OpenSearch Dashboards documentation]({{site.url}}{{site.baseurl}}/opensearch-dashboards/).

_dashboards/install/tls.md

@@ -0,0 +1,41 @@
+---
+layout: default
+title: Configure TLS
+parent: Install OpenSearch Dashboards
+nav_order: 40
+---
+
+# Configure TLS for OpenSearch Dashboards
+
+By default, for ease of testing and getting started, OpenSearch Dashboards runs over HTTP. To enable TLS for HTTPS, update the following settings in `opensearch_dashboards.yml`.
+
+Setting | Description
+:--- | :---
+opensearch.ssl.verificationMode | This setting is for communications between OpenSearch and OpenSearch Dashboards. Valid values are `full`, `certificate`, or `none`. We recommend `full` if you enable TLS, which enables hostname verification. `certificate` just checks the certificate, not the hostname, and `none` performs no checks (suitable for HTTP). Default is `full`.
+opensearch.ssl.certificateAuthorities | If `opensearch.ssl.verificationMode` is `full` or `certificate`, specify the full path (e.g. `[ "/usr/share/opensearch-dashboards-1.0.0/config/root-ca.pem" ]` to the certificate authority for your OpenSearch cluster.
+server.ssl.enabled | This setting is for communications between OpenSearch Dashboards and the web browser. Set to true for HTTPS, false for HTTP.
+server.ssl.certificate | If `server.ssl.enabled` is true, specify the full path (e.g. `/usr/share/opensearch-dashboards-1.0.0/config/my-client-cert.pem` to a valid client certificate for your OpenSearch cluster. You can [generate your own]({{site.url}}{{site.baseurl}}/security-plugin/configuration/generate-certificates/) or get one from a certificate authority.
+server.ssl.key | If `server.ssl.enabled` is true, specify the full path (e.g. `/usr/share/opensearch-dashboards-1.0.0/config/my-client-cert-key.pem` to the key for your client certificate. You can [generate your own]({{site.url}}{{site.baseurl}}/security-plugin/configuration/generate-certificates/) or get one from a certificate authority.
+opensearch_security.cookie.secure | If you enable TLS for OpenSearch Dashboards, change this setting to `true`. For HTTP, set it to `false`.
+
+This `opensearch_dashboards.yml` configuration shows OpenSearch and OpenSearch Dashboards running on the same machine with the demo configuration:
+
+```yml
+opensearch.hosts: ["https://localhost:9200"]
+opensearch.ssl.verificationMode: full
+opensearch.username: "kibanaserver"
+opensearch.password: "kibanaserver"
+opensearch.requestHeadersWhitelist: [ authorization,securitytenant ]
+server.ssl.enabled: true
+server.ssl.certificate: /usr/share/opensearch-1.0.0/config/client-cert.pem
+server.ssl.key: /usr/share/opensearch-1.0.0/config/client-cert-key.pem
+opensearch.ssl.certificateAuthorities: [ "/usr/share/opensearch-1.0.0/config/root-ca.pem" ]
+opensearch_security.multitenancy.enabled: true
+opensearch_security.multitenancy.tenants.preferred: ["Private", "Global"]
+opensearch_security.readonly_mode.roles: ["kibana_read_only"]
+opensearch_security.cookie.secure: true
+```
+
+If you use the Docker install, you can pass a custom `opensearch_dashboards.yml` to the container. To learn more, see the [Docker installation page]({{site.url}}{{site.baseurl}}/opensearch/install/docker/).
+
+After enabling these settings and starting OpenSearch Dashboards, you can connect to it at `https://localhost:5601`. You might have to acknowledge a browser warning if your certificates are self-signed. To avoid this sort of warning (or outright browser incompatibility), best practice is to use certificates from trusted certificate authority.

_dashboards/maptiles.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: WMS map server
-parent: OpenSearch Dashboards
 nav_order: 5
 ---
 

_dashboards/notebooks.md

@@ -0,0 +1,118 @@
+---
+layout: default
+title: Notebooks
+nav_order: 50
+redirect_from: /docs/notebooks/
+has_children: false
+---
+
+# Notebooks
+
+An OpenSearch Dashboards notebook is an interface that lets you easily combine code snippets, live visualizations, and narrative text in a single notebook interface.
+
+Notebooks let you interactively explore data by running different visualizations that you can share with team members to collaborate on a project.
+
+A notebook is a document composed of two elements: code blocks (Markdown/SQL/PPL) and visualizations. Choose multiple timelines to compare and contrast visualizations.
+
+You can also generate [reports]({{site.url}}{{site.baseurl}}/dashboards/reporting/) directly from your notebooks.
+
+Common use cases include creating postmortem reports, designing runbooks, building live infrastructure reports, and writing documentation.
+
+Tenants in OpenSearch Dashboards are spaces for saving notebooks and other OpenSearch Dashboards objects. For more information, see [OpenSearch Dashboards multi-tenancy]({{site.url}}{{site.baseurl}}/security-plugin/access-control/multi-tenancy/).
+{: .note }
+
+
+## Get started with notebooks
+
+To get started, choose **Notebooks** within OpenSearch Dashboards.
+
+
+### Step 1: Create a notebook
+
+A notebook is an interface for creating reports.
+
+1. Choose **Create notebook** and enter a descriptive name.
+1. Choose **Create**.
+
+Choose **Actions** to rename, duplicate, or delete a notebook.
+
+
+### Step 2: Add a paragraph
+
+Paragraphs combine code blocks and visualizations for describing data.
+
+#### Add a code block
+
+Code blocks support markdown, SQL, and PPL languages.
+
+Specify the input language on the first line using `%[language type]` syntax.
+For example, type `%md` for markdown, `%sql` for SQL, and `%ppl` for PPL.
+
+##### Sample markdown block
+
+```
+%md
+Add in text formatted in markdown.
+```
+
+![Markdown paragraph]({{site.url}}{{site.baseurl}}/images/markdown-notebook.png)
+
+##### Sample SQL block
+
+```sql
+%sql
+Select * from opensearch_dashboards_sample_data_flights limit 20;
+```
+
+![SQL paragraph]({{site.url}}{{site.baseurl}}/images/sql-notebook.png)
+
+##### Sample PPL block
+
+```
+%ppl
+source=opensearch_dashboards_sample_data_logs | head 20
+```
+
+![PPL paragraph]({{site.url}}{{site.baseurl}}/images/ppl-notebook.png)
+
+
+#### Add a visualization
+
+1. To add a visualization, choose **Add paragraph** and select **Visualization**.
+1. In **Title**, select your visualization and choose a date range. You can choose multiple timelines to compare and contrast visualizations.
+1. To run and save a paragraph, choose **Run**.
+
+![Visualization paragraph]({{site.url}}{{site.baseurl}}/images/visualization-notebook.png)
+
+## Paragraph actions
+
+You can perform the following actions on paragraphs:
+
+- Add a new paragraph to the top of a report.
+- Add a new paragraph to the bottom of a report.
+- Run all the paragraphs at the same time.
+- Clear the outputs of all paragraphs.
+- Delete all the paragraphs.
+- Move paragraphs up and down.
+
+## Sample notebooks
+
+We prepared the following sample notebooks that showcase a variety of use cases:
+
+- Using SQL to query the OpenSearch Dashboards sample flight data.
+- Using PPL to query the OpenSearch Dashboards sample web logs data.
+- Using PPL and visualizations to perform sample root cause event analysis on the OpenSearch Dashboards sample web logs data.
+
+To add a sample notebook, choose **Actions** and select **Add sample notebooks**.
+
+## Create a report
+
+You can use notebooks to create PNG and PDF reports:
+
+1. From the top menu bar, choose **Reporting actions**.
+1. You can choose to **Download PDF** or **Download PNG**.
+
+   Reports generate asynchronously in the background and might take a few minutes, depending on the size of the report. A notification appears when your report is ready to download.
+
+1. To create a schedule-based report, choose **Create report definition**. For steps to create a report definition, see [Create reports using a definition]({{site.url}}{{site.baseurl}}/dashboards/reporting#create-reports-using-a-definition).
+1. To see all your reports, choose **View all reports**.

_dashboards/reporting.md

@@ -1,14 +1,16 @@
 ---
 layout: default
 title: Reporting
-parent: OpenSearch Dashboards
 nav_order: 20
 ---
 
 
 # Reporting
 
-You can use OpenSearch Dashboards to create PNG, PDF, and CSV reports. To create reports, you must have the correct permissions. For a summary of the predefined roles and the permissions they grant, see the [security plugin](../../security/access-control/users-roles/#predefined-roles).
+You can use OpenSearch Dashboards to create PNG, PDF, and CSV reports. To create reports, you must have the correct permissions. For a summary of the predefined roles and the permissions they grant, see the [security plugin]({{site.url}}{{site.baseurl}}/security-plugin/access-control/users-roles#predefined-roles).
+
+CSV reports have a non-configurable 10,000 row limit. They have no explicit size limit (e.g. in MB), but extremely large documents could cause report generation to fail with an out of memory error from the V8 JavaScript engine.
+{: .tip }
 
 
 ## Create reports from Discovery, Visualize, or Dashboard
@@ -36,7 +38,7 @@ Definitions let you generate reports on a periodic schedule.
 1. (Optional) Add a header or footer to the report. Headers and footers are only available for dashboard or visualization reports.
 1. Under **Report trigger**, choose either **On-demand** or **Schedule**.
 
-   For scheduled reports, select either **Recurring** or **Cron based**. You can receive reports daily or at some other time interval. Cron expressions give you even more flexiblity. See [Cron expression reference](../../alerting/cron/) for more information.
+   For scheduled reports, select either **Recurring** or **Cron based**. You can receive reports daily or at some other time interval. Cron expressions give you even more flexiblity. See [Cron expression reference]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/cron/) for more information.
 
 1. Choose **Create**.
 
@@ -46,7 +48,7 @@ Definitions let you generate reports on a periodic schedule.
 
 While creating a report for dashboards or visualizations, you might see a the following error:
 
-![OpenSearch Dashboards reporting pop-up error message](../../images/reporting-error.png)
+![OpenSearch Dashboards reporting pop-up error message]({{site.url}}{{site.baseurl}}/images/reporting-error.png)
 
 This problem can occur for two reasons:
 

_external_links/javadoc.md

@@ -0,0 +1,7 @@
+---
+layout: default
+title: Javadoc
+nav_order: 1
+permalink: /javadoc/
+redirect_to: https://opensearch.org/docs/javadocs/
+---

_im-plugin/index-rollups/index.md

@@ -1,14 +1,13 @@
 ---
 layout: default
-title: Index Rollups
+title: Index rollups
 nav_order: 35
-parent: Index management
 has_children: true
 redirect_from: /docs/ism/index-rollups/
 has_toc: false
 ---
 
-# Index Rollups
+# Index rollups
 
 Time series data increases storage costs, strains cluster health, and slows down aggregations over time. Index rollup lets you periodically reduce data granularity by rolling up old data into summarized indices.
 
@@ -52,7 +51,7 @@ The order in which you select attributes is critical. A city followed by a demog
 Specify a schedule to roll up your indices as it’s being ingested. The index rollup job is enabled by default.
 
 1. Specify if the data is continuous or not.
-3. For roll up execution frequency, select **Define by fixed interval** and specify the **Rollup interval** and the time unit or **Define by cron expression** and add in a cron expression to select the interval. To learn how to define a cron expression, see [Alerting](../alerting/cron/).
+3. For roll up execution frequency, select **Define by fixed interval** and specify the **Rollup interval** and the time unit or **Define by cron expression** and add in a cron expression to select the interval. To learn how to define a cron expression, see [Alerting]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/cron/).
 4. Specify the number of pages per execution process. A larger number means faster execution and more cost for memory.
 5. (Optional) Add a delay to the roll up executions. This is the amount of time the job waits for data ingestion to accommodate any processing time. For example, if you set this value to 10 minutes, an index rollup that executes at 2 PM to roll up 1 PM to 2 PM of data starts at 2:10 PM.
 6. Choose **Next**.
@@ -63,7 +62,7 @@ Review your configuration and select **Create**.
 
 ### Step 5: Search the target index
 
-You can use the standard `_search` API to search the target index. Make sure that the query matches the constraints of the target index. For example, if don’t set up terms aggregations on a field, you don’t receive results for terms aggregations. If you don’t set up the maximum aggregations, you don’t receive results for maximum aggregations.
+You can use the standard `_search` API to search the target index. Make sure that the query matches the constraints of the target index. For example, if you don’t set up terms aggregations on a field, you don’t receive results for terms aggregations. If you don’t set up the maximum aggregations, you don’t receive results for maximum aggregations.
 
 You can’t access the internal structure of the data in the target index because the plugin automatically rewrites the query in the background to suit the target index. This is to make sure you can use the same query for the source and target index.
 
@@ -219,7 +218,7 @@ Create an index rollup job.
 This example picks the `order_date`, `customer_gender`, `geoip.city_name`, `geoip.region_name`, and `day_of_week` fields and rolls them into an `example_rollup` target index:
 
 ```json
-PUT _opensearch/_rollup/jobs/example
+PUT _plugins/_rollup/jobs/example
 {
   "rollup": {
     "enabled": true,

_im-plugin/index-rollups/rollup-api.md

@@ -1,13 +1,12 @@
 ---
 layout: default
-title: Index Rollups API
-parent: Index Rollups
-grand_parent: Index management
+title: Index rollups API
+parent: Index rollups
 redirect_from: /docs/ism/rollup-api/
 nav_order: 9
 ---
 
-# Index Rollups API
+# Index rollups API
 
 Use the index rollup operations to programmatically work with index rollup jobs.
 
@@ -28,8 +27,8 @@ You must provide the `seq_no` and `primary_term` parameters.
 #### Request
 
 ```json
-PUT _opensearch/_rollup/jobs/<rollup_id> // Create
-PUT _opensearch/_rollup/jobs/<rollup_id>?if_seq_no=1&if_primary_term=1 // Update
+PUT _plugins/_rollup/jobs/<rollup_id> // Create
+PUT _plugins/_rollup/jobs/<rollup_id>?if_seq_no=1&if_primary_term=1 // Update
 {
   "rollup": {
     "source_index": "nyc-taxi-data",
@@ -141,7 +140,7 @@ Returns all information about an index rollup job based on the `rollup_id`.
 #### Request
 
 ```json
-GET _opensearch/_rollup/jobs/<rollup_id>
+GET _plugins/_rollup/jobs/<rollup_id>
 ```
 
 
@@ -166,7 +165,7 @@ Deletes an index rollup job based on the `rollup_id`.
 #### Request
 
 ```json
-DELETE _opensearch/_rollup/jobs/<rollup_id>
+DELETE _plugins/_rollup/jobs/<rollup_id>
 ```
 
 #### Sample response
@@ -185,8 +184,8 @@ Start or stop an index rollup job.
 #### Request
 
 ```json
-POST _opensearch/_rollup/jobs/<rollup_id>/_start
-POST _opensearch/_rollup/jobs/<rollup_id>/_stop
+POST _plugins/_rollup/jobs/<rollup_id>/_start
+POST _plugins/_rollup/jobs/<rollup_id>/_stop
 ```
 
 
@@ -206,7 +205,7 @@ Returns detailed metadata information about the index rollup job and its current
 #### Request
 
 ```json
-GET _opensearch/_rollup/jobs/<rollup_id>/_explain
+GET _plugins/_rollup/jobs/<rollup_id>/_explain
 ```
 
 

_im-plugin/index-transforms/index.md

@@ -0,0 +1,156 @@
+---
+layout: default
+title: Index transforms
+nav_order: 20
+has_children: true
+redirect_from: /docs/im/index-transforms/
+has_toc: false
+---
+
+# Index transforms
+
+Whereas index rollup jobs let you reduce data granularity by rolling up old data into condensed indices, transform jobs let you create a different, summarized view of your data centered around certain fields, so you can visualize or analyze the data in different ways.
+
+For example, suppose that you have airline data that’s scattered across multiple fields and categories, and you want to view a summary of the data that’s organized by airline, quarter, and then price. You can use a transform job to create a new, summarized index that’s organized by those specific categories.
+
+You can use transform jobs in two ways:
+
+1. Use the OpenSearch Dashboards UI to specify the index you want to transform and any optional data filters you want to use to filter the original index. Then select the fields you want to transform and the aggregations to use in the transformation. Finally, define a schedule for your job to follow.
+2. Use the transforms API to specify all the details about your job: the index you want to transform, target groups you want the transformed index to have, any aggregations you want to use to group columns, and a schedule for your job to follow.
+
+OpenSearch Dashboards provides a detailed summary of the jobs you created and their relevant information, such as associated indices and job statuses. You can review and edit your job’s details and selections before creation, and even preview a transformed index’s data as you’re choosing which fields to transform. However, you can also use the REST API to create transform jobs and preview transform job results, but you must know all of the necessary settings and parameters to submit them as part of the HTTP request body. Submitting your transform job configurations as JSON scripts offers you more portability, allowing you to share and replicate your transform jobs, which is harder to do using OpenSearch Dashboards.
+
+Your use cases will help you decide which method to use to create transform jobs.
+
+## Create a transform job
+
+If you don't have any data in your cluster, you can use the sample flight data within OpenSearch Dashboards to try out transform jobs. Otherwise, after launching OpenSearch Dashboards, choose **Index Management**. Select **Transform Jobs**, and choose **Create Transform Job**.
+
+### Step 1: Choose indices
+
+1. In the **Job name and description** section, specify a name and an optional description for your job.
+2. In the **Indices** section, select the source and target index. You can either select an existing target index or create a new one by entering a name for your new index. If you want to transform just a subset of your source index, choose **Add Data Filter**, and use the OpenSearch query DSL to specify a subset of your source index. For more information about the OpenSearch query DSL, see [query DSL]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/).
+3. Choose **Next**.
+
+### Step 2: Select fields to transform
+
+After specifying the indices, you can select the fields you want to use in your transform job, as well as whether to use groupings or aggregations.
+
+You can use groupings to place your data into separate buckets in your transformed index. For example, if you want to group all of the airport destinations within the sample flight data, you can group the `DestAirportID` field into a target field of `DestAirportID_terms` field, and you can find the grouped airport IDs in your transformed index after the transform job finishes.
+
+On the other hand, aggregations let you perform simple calculations. For example, you can include an aggregation in your transform job to define a new field of `sum_of_total_ticket_price` that calculates the sum of all airplane tickets, and then analyze the newly summer data within your transformed index.
+
+1. In the data table, select the fields you want to transform and expand the drop-down menu within the column header to choose the grouping or aggregation you want to use.
+
+    Currently, transform jobs support histogram, date_histogram, and terms groupings. For more information about groupings, see [Bucket Aggregations]({{site.url}}{{site.baseurl}}/opensearch/bucket-agg/). In terms of aggregations, you can select from `sum`, `avg`, `max`, `min`, `value_count`, `percentiles`, and `scripted_metric`. For more information about aggregations, see [Metric Aggregations]({{site.url}}{{site.baseurl}}/opensearch/metric-agg/).
+
+2. Repeat step 1 for any other fields that you want to transform.
+3. After selecting the fields that you want to transform and verifying the transformation, choose **Next**.
+
+### Step 3: Specify a schedule
+
+You can configure transform jobs to run once or multiple times on a schedule. Transform jobs are enabled by default.
+
+1. For **transformation execution frequency**, select **Define by fixed interval** and specify a **transform interval**.
+2. Under **Advanced**, specify an optional amount for **Pages per execution**. A larger number means more data is processed in each search request, but also uses more memory and causes higher latency. Exceeding allowed memory limits can cause exceptions and errors to occur.
+3. Choose **Next**.
+
+### Step 4: Review and confirm details
+
+After confirming your transform job’s details are correct, choose **Create Transform Job**. If you want to edit any part of the job, choose **Edit** of the section you want to change, and make the necessary changes. You can’t change aggregations or groupings after creating a job.
+
+### Step 5: Search through the transformed index.
+
+Once the transform job finishes, you can use the `_search` API operation to search the target index.
+
+```json
+GET <target_index>/_search
+```
+
+For example, after running a transform job that transforms the flight data based on a `DestAirportID` field, you can run the following request that returns all of the fields that have a value of `SFO`.
+
+**Sample Request**
+
+```json
+GET finished_flight_job/_search
+{
+  "query": {
+    "match": {
+      "DestAirportID_terms" : "SFO"
+    }
+  }
+}
+```
+
+**Sample Response**
+
+```json
+{
+  "took" : 3,
+  "timed_out" : false,
+  "_shards" : {
+    "total" : 5,
+    "successful" : 5,
+    "skipped" : 0,
+    "failed" : 0
+  },
+  "hits" : {
+    "total" : {
+      "value" : 4,
+      "relation" : "eq"
+    },
+    "max_score" : 3.845883,
+    "hits" : [
+      {
+        "_index" : "finished_flight_job",
+        "_type" : "_doc",
+        "_id" : "dSNKGb8U3OJOmC4RqVCi1Q",
+        "_score" : 3.845883,
+        "_source" : {
+          "transform._id" : "sample_flight_job",
+          "transform._doc_count" : 14,
+          "Carrier_terms" : "Dashboards Airlines",
+          "DestAirportID_terms" : "SFO"
+        }
+      },
+      {
+        "_index" : "finished_flight_job",
+        "_type" : "_doc",
+        "_id" : "_D7oqOy7drx9E-MG96U5RA",
+        "_score" : 3.845883,
+        "_source" : {
+          "transform._id" : "sample_flight_job",
+          "transform._doc_count" : 14,
+          "Carrier_terms" : "Logstash Airways",
+          "DestAirportID_terms" : "SFO"
+        }
+      },
+      {
+        "_index" : "finished_flight_job",
+        "_type" : "_doc",
+        "_id" : "YuZ8tOt1OsBA54e84WuAEw",
+        "_score" : 3.6988301,
+        "_source" : {
+          "transform._id" : "sample_flight_job",
+          "transform._doc_count" : 11,
+          "Carrier_terms" : "ES-Air",
+          "DestAirportID_terms" : "SFO"
+        }
+      },
+      {
+        "_index" : "finished_flight_job",
+        "_type" : "_doc",
+        "_id" : "W_-e7bVmH6eu8veJeK8ZxQ",
+        "_score" : 3.6988301,
+        "_source" : {
+          "transform._id" : "sample_flight_job",
+          "transform._doc_count" : 10,
+          "Carrier_terms" : "JetBeats",
+          "DestAirportID_terms" : "SFO"
+        }
+      }
+    ]
+  }
+}
+
+```

_im-plugin/index-transforms/transforms-apis.md

@@ -0,0 +1,713 @@
+---
+layout: default
+title: Transforms APIs
+nav_order: 45
+parent: Index transforms
+has_toc: true
+---
+
+# Transforms APIs
+
+Aside from using OpenSearch Dashboards, you can also use the REST API to create, start, stop, and complete other operations relative to transform jobs.
+
+#### Table of contents
+- TOC
+{:toc}
+
+## Create a transform job
+
+Creates a transform job.
+
+**Sample Request**
+
+```json
+PUT _plugins/_transform/<transform_id>
+
+{
+  "transform": {
+  "enabled": true,
+  "schedule": {
+    "interval": {
+    "period": 1,
+    "unit": "Minutes",
+    "start_time": 1602100553
+    }
+  },
+  "description": "Sample transform job",
+  "source_index": "sample_index",
+  "target_index": "sample_target",
+  "data_selection_query": {
+    "match_all": {}
+  },
+  "page_size": 1,
+  "groups": [
+    {
+    "terms": {
+      "source_field": "customer_gender",
+      "target_field": "gender"
+    }
+    },
+    {
+    "terms": {
+      "source_field": "day_of_week",
+      "target_field": "day"
+    }
+    }
+  ],
+  "aggregations": {
+    "quantity": {
+    "sum": {
+      "field": "total_quantity"
+    }
+    }
+  }
+  }
+}
+```
+
+**Sample Response**
+
+```json
+{
+  "_id": "sample",
+  "_version": 7,
+  "_seq_no": 13,
+  "_primary_term": 1,
+  "transform": {
+    "transform_id": "sample",
+    "schema_version": 7,
+    "schedule": {
+      "interval": {
+        "start_time": 1621467964243,
+        "period": 1,
+        "unit": "Minutes"
+      }
+    },
+    "metadata_id": null,
+    "updated_at": 1621467964243,
+    "enabled": true,
+    "enabled_at": 1621467964243,
+    "description": "Sample transform job",
+    "source_index": "sample_index",
+    "data_selection_query": {
+      "match_all": {
+        "boost": 1.0
+      }
+    },
+    "target_index": "sample_target",
+    "roles": [],
+    "page_size": 1,
+    "groups": [
+      {
+        "terms": {
+          "source_field": "customer_gender",
+          "target_field": "gender"
+        }
+      },
+      {
+        "terms": {
+          "source_field": "day_of_week",
+          "target_field": "day"
+        }
+      }
+    ],
+    "aggregations": {
+      "quantity": {
+        "sum": {
+          "field": "total_quantity"
+        }
+      }
+    }
+  }
+}
+```
+You can specify the following options in the HTTP request body:
+
+Option | Data Type | Description | Required
+:--- | :--- | :--- | :---
+enabled | Boolean | If true, the transform job is enabled at creation. | No
+schedule | JSON | The schedule the transform job runs on. | Yes
+start_time | Integer | The Unix epoch time of the transform job's start time. | Yes
+description | String | Describes the transform job. | No
+metadata_id | String | Any metadata to be associated with the transform job. | No
+source_index | String | The source index whose data to transform. | Yes
+target_index | String | The target index the newly transformed data is added into. You can create a new index or update an existing one. | Yes
+data_selection_query | JSON | The query DSL to use to filter a subset of the source index for the transform job. See [query DSL]({{site.url}}{{site.baseurl}}/opensearch/query-dsl) for more information. | Yes
+page_size | Integer | The number of fields to transform at a time. Higher number means higher performance but requires more memory and can cause higher latency. (Default: 1) | Yes
+groups | Array | Specifies the grouping(s) to use in the transform job. Supported groups are `terms`, `histogram`, and `date_histogram`. For more information, see [Bucket Aggregations]({{site.url}}{{site.baseurl}}/opensearch/bucket-agg). | Yes if not using aggregations
+source_field | String | The field(s) to transform | Yes
+aggregations | JSON | The aggregations to use in the transform job. Supported aggregations are: `sum`, `max`, `min`, `value_count`, `avg`, `scripted_metric`, and `percentiles`. For more information, see [Metric Aggregations]({{site.url}}{{site.baseurl}}/opensearch/metric-agg). | Yes if not using groups
+
+## Update a transform job
+
+Updates a transform job if `transform_id` already exists.
+
+**Sample Request**
+
+```json
+PUT _plugins/_transform/<transform_id>
+
+{
+  "transform": {
+  "enabled": true,
+  "schedule": {
+    "interval": {
+    "period": 1,
+    "unit": "Minutes",
+    "start_time": 1602100553
+    }
+  },
+  "description": "Sample transform job",
+  "source_index": "sample_index",
+  "target_index": "sample_target",
+  "data_selection_query": {
+    "match_all": {}
+  },
+  "page_size": 1,
+  "groups": [
+    {
+    "terms": {
+      "source_field": "customer_gender",
+      "target_field": "gender"
+    }
+    },
+    {
+    "terms": {
+      "source_field": "day_of_week",
+      "target_field": "day"
+    }
+    }
+  ],
+  "aggregations": {
+    "quantity": {
+    "sum": {
+      "field": "total_quantity"
+    }
+    }
+  }
+  }
+}
+```
+
+**Sample Response**
+
+```json
+{
+  "_id": "sample",
+  "_version": 2,
+  "_seq_no": 14,
+  "_primary_term": 1,
+  "transform": {
+    "transform_id": "sample",
+    "schema_version": 7,
+    "schedule": {
+      "interval": {
+        "start_time": 1602100553,
+        "period": 1,
+        "unit": "Minutes"
+      }
+    },
+    "metadata_id": null,
+    "updated_at": 1621889843874,
+    "enabled": true,
+    "enabled_at": 1621889843874,
+    "description": "Sample transform job",
+    "source_index": "sample_index",
+    "data_selection_query": {
+      "match_all": {
+        "boost": 1.0
+      }
+    },
+    "target_index": "sample_target",
+    "roles": [],
+    "page_size": 1,
+    "groups": [
+      {
+        "terms": {
+          "source_field": "customer_gender",
+          "target_field": "gender"
+        }
+      },
+      {
+        "terms": {
+          "source_field": "day_of_week",
+          "target_field": "day"
+        }
+      }
+    ],
+    "aggregations": {
+      "quantity": {
+        "sum": {
+          "field": "total_quantity"
+        }
+      }
+    }
+  }
+}
+```
+
+The `Update` operation supports the following URL parameters:
+
+Parameter | Description | Required
+:---| :--- | :---
+`if_seq_no` | Only perform the transform operation if the last operation that changed the transform job has the specified sequence number. | No
+`if_primary_term` | Only perform the transform operation if the last operation that changed the transform job has the specified sequence term. | No
+
+## Get a transform job's details
+
+Returns a transform job's details.
+
+**Sample Request**
+
+```json
+GET _plugins/_transform/<transform_id>
+```
+
+**Sample Response**
+
+```json
+{
+  "_id": "sample",
+  "_version": 7,
+  "_seq_no": 13,
+  "_primary_term": 1,
+  "transform": {
+    "transform_id": "sample",
+    "schema_version": 7,
+    "schedule": {
+      "interval": {
+        "start_time": 1621467964243,
+        "period": 1,
+        "unit": "Minutes"
+      }
+    },
+    "metadata_id": null,
+    "updated_at": 1621467964243,
+    "enabled": true,
+    "enabled_at": 1621467964243,
+    "description": "Sample transform job",
+    "source_index": "sample_index",
+    "data_selection_query": {
+      "match_all": {
+        "boost": 1.0
+      }
+    },
+    "target_index": "sample_target",
+    "roles": [],
+    "page_size": 1,
+    "groups": [
+      {
+        "terms": {
+          "source_field": "customer_gender",
+          "target_field": "gender"
+        }
+      },
+      {
+        "terms": {
+          "source_field": "day_of_week",
+          "target_field": "day"
+        }
+      }
+    ],
+    "aggregations": {
+      "quantity": {
+        "sum": {
+          "field": "total_quantity"
+        }
+      }
+    }
+  }
+}
+```
+
+You can also get details of all transform jobs by omitting `transform_id`.
+
+**Sample Request**
+
+```json
+GET _plugins/_transform/
+```
+
+**Sample Response**
+
+```json
+{
+  "total_transforms": 1,
+  "transforms": [
+    {
+      "_id": "sample",
+      "_seq_no": 13,
+      "_primary_term": 1,
+      "transform": {
+        "transform_id": "sample",
+        "schema_version": 7,
+        "schedule": {
+          "interval": {
+            "start_time": 1621467964243,
+            "period": 1,
+            "unit": "Minutes"
+          }
+        },
+        "metadata_id": null,
+        "updated_at": 1621467964243,
+        "enabled": true,
+        "enabled_at": 1621467964243,
+        "description": "Sample transform job",
+        "source_index": "sample_index",
+        "data_selection_query": {
+          "match_all": {
+            "boost": 1.0
+          }
+        },
+        "target_index": "sample_target",
+        "roles": [],
+        "page_size": 1,
+        "groups": [
+          {
+            "terms": {
+              "source_field": "customer_gender",
+              "target_field": "gender"
+            }
+          },
+          {
+            "terms": {
+              "source_field": "day_of_week",
+              "target_field": "day"
+            }
+          }
+        ],
+        "aggregations": {
+          "quantity": {
+            "sum": {
+              "field": "total_quantity"
+            }
+          }
+        }
+      }
+    }
+  ]
+}
+```
+
+You can specify these options as the `GET` API operation’s URL parameters to filter results:
+
+Parameter | Description | Required
+:--- | :--- | :---
+from | The starting index to search from. (Default: 0) | No
+size | Specifies the amount of results to return (Default: 10) | No
+search |The search term to use to filter results. | No
+sortField | The field to sort results with. | No
+sortDirection | Specifies the direction to sort results in. Can be `ASC` or `DESC`. (Default: ASC) | No
+
+For example, this request returns two results starting from the eighth index.
+
+**Sample Request**
+
+```json
+GET _plugins/_transform?size=2&from=8
+```
+
+**Sample Response**
+
+```json
+{
+  "total_transforms": 18,
+  "transforms": [
+    {
+      "_id": "sample8",
+      "_seq_no": 93,
+      "_primary_term": 1,
+      "transform": {
+        "transform_id": "sample8",
+        "schema_version": 7,
+        "schedule": {
+          "interval": {
+            "start_time": 1622063596812,
+            "period": 1,
+            "unit": "Minutes"
+          }
+        },
+        "metadata_id": "y4hFAB2ZURQ2dzY7BAMxWA",
+        "updated_at": 1622063657233,
+        "enabled": false,
+        "enabled_at": null,
+        "description": "Sample transform job",
+        "source_index": "sample_index3",
+        "data_selection_query": {
+          "match_all": {
+            "boost": 1.0
+          }
+        },
+        "target_index": "sample_target3",
+        "roles": [],
+        "page_size": 1,
+        "groups": [
+          {
+            "terms": {
+              "source_field": "customer_gender",
+              "target_field": "gender"
+            }
+          },
+          {
+            "terms": {
+              "source_field": "day_of_week",
+              "target_field": "day"
+            }
+          }
+        ],
+        "aggregations": {
+          "quantity": {
+            "sum": {
+              "field": "total_quantity"
+            }
+          }
+        }
+      }
+    },
+    {
+      "_id": "sample9",
+      "_seq_no": 98,
+      "_primary_term": 1,
+      "transform": {
+        "transform_id": "sample9",
+        "schema_version": 7,
+        "schedule": {
+          "interval": {
+            "start_time": 1622063598065,
+            "period": 1,
+            "unit": "Minutes"
+          }
+        },
+        "metadata_id": "x8tCIiYMTE3veSbIJkit5A",
+        "updated_at": 1622063658388,
+        "enabled": false,
+        "enabled_at": null,
+        "description": "Sample transform job",
+        "source_index": "sample_index4",
+        "data_selection_query": {
+          "match_all": {
+            "boost": 1.0
+          }
+        },
+        "target_index": "sample_target4",
+        "roles": [],
+        "page_size": 1,
+        "groups": [
+          {
+            "terms": {
+              "source_field": "customer_gender",
+              "target_field": "gender"
+            }
+          },
+          {
+            "terms": {
+              "source_field": "day_of_week",
+              "target_field": "day"
+            }
+          }
+        ],
+        "aggregations": {
+          "quantity": {
+            "sum": {
+              "field": "total_quantity"
+            }
+          }
+        }
+      }
+    }
+  ]
+}
+```
+
+## Start a transform job
+
+Transform jobs created using the API are automatically enabled, but if you ever need to enable a job, you can use the `start` API operation.
+
+**Sample Request**
+
+```json
+POST _plugins/_transform/<transform_id>/_start
+```
+
+**Sample Response**
+
+```json
+{
+  "acknowledged": true
+}
+```
+
+## Stop a transform job
+
+Stops/disables a transform job.
+
+**Sample Request**
+
+```json
+POST _plugins/_transform/<transform_id>/_stop
+```
+
+**Sample Response**
+
+```json
+{
+  "acknowledged": true
+}
+```
+
+## Get the status of a transform job
+
+Returns the status and metadata of a transform job.
+
+**Sample Request**
+
+```json
+GET _plugins/_transform/<transform_id>/_explain
+```
+
+**Sample Response**
+
+```json
+{
+  "sample": {
+    "metadata_id": "PzmjweME5xbgkenl9UpsYw",
+    "transform_metadata": {
+      "transform_id": "sample",
+      "last_updated_at": 1621883525873,
+      "status": "finished",
+      "failure_reason": "null",
+      "stats": {
+        "pages_processed": 0,
+        "documents_processed": 0,
+        "documents_indexed": 0,
+        "index_time_in_millis": 0,
+        "search_time_in_millis": 0
+      }
+    }
+  }
+}
+```
+
+## Preview a transform job's results
+
+Returns a preview of what a transformed index would look like.
+
+**Sample Request**
+
+```json
+POST _plugins/_transform/_preview
+
+{
+  "transform": {
+  "enabled": false,
+  "schedule": {
+    "interval": {
+    "period": 1,
+    "unit": "Minutes",
+    "start_time": 1602100553
+    }
+  },
+  "description": "test transform",
+  "source_index": "sample_index",
+  "target_index": "sample_target",
+  "data_selection_query": {
+    "match_all": {}
+  },
+  "page_size": 10,
+  "groups": [
+    {
+    "terms": {
+      "source_field": "customer_gender",
+      "target_field": "gender"
+    }
+    },
+    {
+    "terms": {
+      "source_field": "day_of_week",
+      "target_field": "day"
+    }
+    }
+  ],
+  "aggregations": {
+    "quantity": {
+    "sum": {
+      "field": "total_quantity"
+    }
+    }
+  }
+  }
+}
+```
+
+**Sample Response**
+
+```json
+{
+  "documents" : [
+  {
+    "quantity" : 862.0,
+    "gender" : "FEMALE",
+    "day" : "Friday"
+  },
+  {
+    "quantity" : 682.0,
+    "gender" : "FEMALE",
+    "day" : "Monday"
+  },
+  {
+    "quantity" : 772.0,
+    "gender" : "FEMALE",
+    "day" : "Saturday"
+  },
+  {
+    "quantity" : 669.0,
+    "gender" : "FEMALE",
+    "day" : "Sunday"
+  },
+  {
+    "quantity" : 887.0,
+    "gender" : "FEMALE",
+    "day" : "Thursday"
+  }
+  ]
+}
+```
+
+## Delete a transform job
+
+Deletes a transform job. This operation does not delete the source or target indices.
+
+**Sample Request**
+
+```json
+DELETE _plugins/_transform/<transform_id>
+```
+
+**Sample Response**
+
+```json
+{
+  "took": 205,
+  "errors": false,
+  "items": [
+    {
+      "delete": {
+        "_index": ".opensearch-ism-config",
+        "_type": "_doc",
+        "_id": "sample",
+        "_version": 4,
+        "result": "deleted",
+        "forced_refresh": true,
+        "_shards": {
+          "total": 2,
+          "successful": 1,
+          "failed": 0
+        },
+        "_seq_no": 6,
+        "_primary_term": 1,
+        "status": 200
+      }
+    }
+  ]
+}
+```

_im-plugin/index.md

@@ -1,11 +1,13 @@
 ---
 layout: default
-title: Index management
-nav_order: 30
-has_children: true
+title: About Index Management
+nav_order: 1
+has_children: false
+redirect_from:
+  - /im-plugin/
 ---
 
-# Index Management
+# About Index Management
 OpenSearch Dashboards
 {: .label .label-yellow :}
 

_im-plugin/ism/api.md

@@ -2,7 +2,6 @@
 layout: default
 title: ISM API
 parent: Index State Management
-grand_parent: Index management
 redirect_from: /docs/ism/api/
 nav_order: 5
 ---
@@ -28,7 +27,7 @@ Creates a policy.
 #### Request
 
 ```json
-PUT _opensearch/_ism/policies/policy_1
+PUT _plugins/_ism/policies/policy_1
 {
   "policy": {
     "description": "ingesting logs",
@@ -145,7 +144,7 @@ Adds a policy to an index. This operation does not change the policy if the inde
 #### Request
 
 ```json
-POST _opensearch/_ism/add/index_1
+POST _plugins/_ism/add/index_1
 {
   "policy_id": "policy_1"
 }
@@ -171,7 +170,7 @@ Updates a policy. Use the `seq_no` and `primary_term` parameters to update an ex
 #### Request
 
 ```json
-PUT _opensearch/_ism/policies/policy_1?if_seq_no=7&if_primary_term=1
+PUT _plugins/_ism/policies/policy_1?if_seq_no=7&if_primary_term=1
 {
   "policy": {
     "description": "ingesting logs",
@@ -288,7 +287,7 @@ Gets the policy by `policy_id`.
 #### Request
 
 ```json
-GET _opensearch/_ism/policies/policy_1
+GET _plugins/_ism/policies/policy_1
 ```
 
 
@@ -358,7 +357,7 @@ Removes any ISM policy from the index.
 #### Request
 
 ```json
-POST _opensearch/_ism/remove/index_1
+POST _plugins/_ism/remove/index_1
 ```
 
 
@@ -385,7 +384,7 @@ In this example, the policy applied on the `index_1` index is changed to `policy
 #### Request
 
 ```json
-POST _opensearch/_ism/change_policy/index_1
+POST _plugins/_ism/change_policy/index_1
 {
   "policy_id": "policy_1",
   "state": "delete",
@@ -417,7 +416,7 @@ Retries the failed action for an index. For the retry call to succeed, ISM must
 #### Request
 
 ```json
-POST _opensearch/_ism/retry/index_1
+POST _plugins/_ism/retry/index_1
 {
   "state": "delete"
 }
@@ -443,7 +442,7 @@ Gets the current state of the index. You can use index patterns to get the statu
 #### Request
 
 ```json
-GET _opensearch/_ism/explain/index_1
+GET _plugins/_ism/explain/index_1
 ```
 
 
@@ -452,13 +451,12 @@ GET _opensearch/_ism/explain/index_1
 ```json
 {
   "index_1": {
-    "index.opendistro.index_state_management.policy_id": "policy_1"
+    "index.plugins.index_state_management.policy_id": "policy_1"
   }
 }
 ```
 
-The `opendistro.index_state_management.policy_id` setting is deprecated starting from version 1.13.0.
-We retain this field in the response API for consistency. 
+The `plugins.index_state_management.policy_id` setting is deprecated starting from ODFE version 1.13.0. We retain this field in the response API for consistency.
 
 ---
 
@@ -469,7 +467,7 @@ Deletes the policy by `policy_id`.
 #### Request
 
 ```json
-DELETE _opensearch/_ism/policies/policy_1
+DELETE _plugins/_ism/policies/policy_1
 ```
 
 

_im-plugin/ism/index.md

@@ -2,9 +2,10 @@
 layout: default
 title: Index State Management
 nav_order: 3
-parent: Index management
 has_children: true
-redirect_from: /docs/ism/
+redirect_from:
+  - /docs/im/ism/
+  - /docs/ism/
 has_toc: false
 ---
 
@@ -20,7 +21,7 @@ For example, you can define a policy that moves your index into a `read_only` st
 
 You might want to perform an index rollover after a certain amount of time or run a `force_merge` operation on an index during off-peak hours to improve search performance during peak hours.
 
-To use the ISM plugin, your user role needs to be mapped to the `all_access` role that gives you full access to the cluster. To learn more, see [Users and roles](../security/access-control/users-roles/).
+To use the ISM plugin, your user role needs to be mapped to the `all_access` role that gives you full access to the cluster. To learn more, see [Users and roles]({{site.url}}{{site.baseurl}}/security-plugin/access-control/users-roles/).
 {: .note }
 
 ## Get started with ISM
@@ -29,7 +30,7 @@ To get started, choose **Index Management** in OpenSearch Dashboards.
 
 ### Step 1: Set up policies
 
-A policy is a set of rules that describes how an index should be managed. For information about creating a policy, see [Policies](policies/).
+A policy is a set of rules that describes how an index should be managed. For information about creating a policy, see [Policies]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies/).
 
 1. Choose the **Index Policies** tab.
 2. Choose **Create policy**.
@@ -41,7 +42,7 @@ After you create a policy, your next step is to attach this policy to an index o
 You can set up an `ism_template` in the policy so when you create an index that matches the ISM template pattern, the index will have this policy attached to it:
 
 ```json
-PUT _opensearch/_ism/policies/policy_id
+PUT _plugins/_ism/policies/policy_id
 {
   "policy": {
     "description": "Example policy.",
@@ -55,7 +56,7 @@ PUT _opensearch/_ism/policies/policy_id
 }
 ```
 
-For an example ISM template policy, see [Sample policy with ISM template](policies/#sample-policy-with-ism-template).
+For an example ISM template policy, see [Sample policy with ISM template]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies#sample-policy-with-ism-template).
 
 Older versions of the plugin include the `policy_id` in an index template, so when an index is created that matches the index template pattern, the index will have the policy attached to it:
 
@@ -84,20 +85,20 @@ The `opendistro.index_state_management.policy_id` setting is deprecated. You can
 4. From the **Policy ID** menu, choose the policy that you created.
 You can see a preview of your policy.
 5. If your policy includes a rollover operation, specify a rollover alias.
-Make sure that the alias that you enter already exists. For more information about the rollover operation, see [rollover](policies/#rollover).
+Make sure that the alias that you enter already exists. For more information about the rollover operation, see [rollover]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies#rollover).
 6. Choose **Apply**.
 
-After you attach a policy to an index, ISM creates a job that runs every 5 minutes by default to perform policy actions, check conditions, and transition the index into different states. To change the default time interval for this job, see [Settings](settings/).
+After you attach a policy to an index, ISM creates a job that runs every 5 minutes by default to perform policy actions, check conditions, and transition the index into different states. To change the default time interval for this job, see [Settings]({{site.url}}{{site.baseurl}}/im-plugin/ism/settings/).
 
-If you want to use an OpenSearch operation to create an index with a policy already attached to it, see [create index](api/#create-index).
+If you want to use an OpenSearch operation to create an index with a policy already attached to it, see [create index]({{site.url}}{{site.baseurl}}/im-plugin/ism/api#create-index).
 
 ### Step 3: Manage indices
 
 1. Choose **Managed Indices**.
-2. To change your policy, see [Change Policy](managedindices/#change-policy).
+2. To change your policy, see [Change Policy]({{site.url}}{{site.baseurl}}/im-plugin/ism/managedindices#change-policy).
 3. To attach a rollover alias to your index, select your policy and choose **Add rollover alias**.
-Make sure that the alias that you enter already exists. For more information about the rollover operation, see [rollover](policies/#rollover).
+Make sure that the alias that you enter already exists. For more information about the rollover operation, see [rollover]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies#rollover).
 4. To remove a policy, choose your policy, and then choose **Remove policy**.
 5. To retry a policy, choose your policy, and then choose **Retry policy**.
 
-For information about managing your policies, see [Managed Indices](managedindices/).
+For information about managing your policies, see [Managed Indices]({{site.url}}{{site.baseurl}}/im-plugin/ism/managedindices/).

_im-plugin/ism/managedindices.md

@@ -3,7 +3,6 @@ layout: default
 title: Managed Indices
 nav_order: 3
 parent: Index State Management
-grand_parent: Index management
 redirect_from: /docs/ism/managedindices/
 has_children: false
 ---

_im-plugin/ism/policies.md

@@ -3,7 +3,6 @@ layout: default
 title: Policies
 nav_order: 1
 parent: Index State Management
-grand_parent: Index management
 redirect_from: /docs/ism/policies/
 has_children: false
 ---
@@ -89,7 +88,7 @@ The following example action has a timeout period of one hour. The policy retrie
 }
 ```
 
-For a list of available unit types, see [Supported units](../../../opensearch/units/).
+For a list of available unit types, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
 
 ## ISM supported operations
 
@@ -160,7 +159,7 @@ Parameter | Description | Type | Required
 }
 ```
 
-For information about setting replicas, see [Primary and replica shards](../../../opensearch/#primary-and-replica-shards).
+For information about setting replicas, see [Primary and replica shards]({{site.url}}{{site.baseurl}}/opensearch#primary-and-replica-shards).
 
 ### close
 
@@ -201,7 +200,7 @@ Deletes a managed index.
 Rolls an alias over to a new index when the managed index meets one of the rollover conditions.
 
 The index format must match the pattern: `^.*-\d+$`. For example, `(logs-000001)`.
-Set `index.opendistro.index_state_management.rollover_alias` as the alias to rollover.
+Set `index.plugins.index_state_management.rollover_alias` as the alias to rollover.
 
 Parameter | Description | Type | Example | Required
 :--- | :--- |:--- |:--- |
@@ -309,7 +308,7 @@ Parameter | Description | Type
 
 ### snapshot
 
-Backup your cluster’s indices and state. For more information about snapshots, see [Take and restore snapshots](../../../opensearch/snapshot-restore/).
+Backup your cluster’s indices and state. For more information about snapshots, see [Take and restore snapshots]({{site.url}}{{site.baseurl}}/opensearch/snapshot-restore/).
 
 The `snapshot` operation has the following parameters:
 
@@ -436,7 +435,7 @@ Note that this condition does not execute at exactly 5:00 PM; the job still exec
 
 A window of an hour, which this example uses, is generally sufficient, but you might increase it to 2--3 hours to avoid missing the window and having to wait a week for the transition to occur. Alternately, you could use a broader expression such as `* * * * SAT,SUN` to have the transition occur at any time during the weekend.
 
-For information on writing cron expressions, see [Cron expression reference](../../../alerting/cron/).
+For information on writing cron expressions, see [Cron expression reference]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/cron/).
 
 ---
 
@@ -526,7 +525,7 @@ The following sample template policy is for a rollover use case.
 1. Create a policy with an `ism_template` field:
 
    ```json
-   PUT _opensearch/_ism/policies/rollover_policy
+   PUT _plugins/_ism/policies/rollover_policy
    {
      "policy": {
        "description": "Example rollover policy.",
@@ -561,7 +560,7 @@ The following sample template policy is for a rollover use case.
    {
      "index_patterns": ["log*"],
      "settings": {
-       "opendistro.index_state_management.rollover_alias": "log"
+       "plugins.index_state_management.rollover_alias": "log"
      }
    }
    ```
@@ -663,4 +662,4 @@ After 30 days, the policy moves this index into a `delete` state. The service se
 
 This diagram shows the `states`, `transitions`, and `actions` of the above policy as a finite-state machine. For more information about finite-state machines, see [Wikipedia](https://en.wikipedia.org/wiki/Finite-state_machine).  
 
-![Policy State Machine](../../images/ism.png)
+![Policy State Machine]({{site.baseurl}}/images/ism.png)

_im-plugin/ism/settings.md

@@ -0,0 +1,49 @@
+---
+layout: default
+title: Settings
+parent: Index State Management
+redirect_from: /docs/ism/settings/
+nav_order: 4
+---
+
+# ISM settings
+
+We don't recommend changing these settings; the defaults should work well for most use cases.
+
+Index State Management (ISM) stores its configuration in the `.opendistro-ism-config` index. Don't modify this index without using the [ISM API operations]({{site.url}}{{site.baseurl}}/im-plugin/ism/api/).
+
+All settings are available using the OpenSearch `_cluster/settings` operation. None require a restart, and all can be marked `persistent` or `transient`.
+
+Setting | Default | Description
+:--- | :--- | :---
+`plugins.index_state_management.enabled` | True | Specifies whether ISM is enabled or not.
+`plugins.index_state_management.job_interval` | 5 minutes | The interval at which the managed index jobs are run.
+`plugins.index_state_management.coordinator.sweep_period` | 10 minutes | How often the routine background sweep is run.
+`plugins.index_state_management.coordinator.backoff_millis` | 50 milliseconds | The backoff time between retries for failures in the `ManagedIndexCoordinator` (such as when we update managed indices).
+`plugins.index_state_management.coordinator.backoff_count` | 2 | The count of retries for failures in the `ManagedIndexCoordinator`.
+`plugins.index_state_management.history.enabled` | True | Specifies whether audit history is enabled or not. The logs from ISM are automatically indexed to a logs document.
+`plugins.index_state_management.history.max_docs` | 2,500,000 | The maximum number of documents before rolling over the audit history index.
+`plugins.index_state_management.history.max_age` | 24 hours | The maximum age before rolling over the audit history index.
+`plugins.index_state_management.history.rollover_check_period` | 8 hours | The time between rollover checks for the audit history index.
+`plugins.index_state_management.history.rollover_retention_period` | 30 days | How long audit history indices are kept.
+`plugins.index_state_management.allow_list` | All actions | List of actions that you can use.
+
+
+## Audit history indices
+
+If you don't want to disable ISM audit history or shorten the retention period, you can create an [index template]({{site.url}}{{site.baseurl}}/opensearch/index-templates/) to reduce the shard count of the history indices:
+
+```json
+PUT _index_template/ism_history_indices
+{
+  "index_patterns": [
+    ".opendistro-ism-managed-index-history-*"
+  ],
+  "template": {
+    "settings": {
+      "number_of_shards": 1,
+      "number_of_replicas": 0
+    }
+  }
+}
+```

_im-plugin/refresh-analyzer/index.md

@@ -1,8 +1,7 @@
 ---
 layout: default
-title: Refresh Search Analyzer
+title: Refresh search analyzer
 nav_order: 40
-parent: Index management
 has_children: false
 redirect_from: /docs/ism/refresh-analyzer/
 has_toc: false
@@ -13,7 +12,7 @@ has_toc: false
 With ISM installed, you can refresh search analyzers in real time with the following API:
 
 ```json
-POST /_opensearch/_refresh_search_analyzers/<index or alias or wildcard>
+POST /_plugins/_refresh_search_analyzers/<index or alias or wildcard>
 ```
 For example, if you change the synonym list in your analyzer, the change takes effect without you needing to close and reopen the index.
 

_includes/nav.html

@@ -60,7 +60,7 @@
   {%- for node in pages_list -%}
     {%- if node.parent == nil -%}
       {%- unless node.nav_exclude -%}
-      <li class="nav-list-item{% if page.url == node.url or page.parent == node.title or page.grand_parent == node.title %} active{% endif %}">
+      <li class="nav-list-item{% if page.collection == include.key and page.url == node.url or page.parent == node.title or page.grand_parent == node.title %} active{% endif %}">
         {%- if node.has_children -%}
           <a href="#" class="nav-list-expander"><svg viewBox="0 0 24 24"><use xlink:href="#svg-arrow-right"></use></svg></a>
         {%- endif -%}
@@ -90,14 +90,36 @@
             </li>
             {%- endunless -%}
           {%- endfor -%}
-
           </ul>
         {%- endif -%}
       </li>
       {%- endunless -%}
     {%- endif -%}
   {%- endfor -%}
-  <li class="nav-list-item">
-    <a href="https://opensearch.org/docs/javadocs/" target="_blank" class="nav-list-link">Javadoc <svg class="external-arrow" width="16" height="16" fill="#002A3A"><use xlink:href="#external-arrow"></use></svg></a>
-  </li>
 </ul>
+
+{%- if page.collection == include.key -%}
+
+  {%- for node in pages_list -%}
+    {%- if node.parent == nil -%}
+      {%- if page.parent == node.title or page.grand_parent == node.title -%}
+        {%- assign first_level_url = node.url | absolute_url -%}
+      {%- endif -%}
+      {%- if node.has_children -%}
+        {%- assign children_list = pages_list | where: "parent", node.title -%}
+        {%- for child in children_list -%}
+          {%- if child.has_children -%}
+            {%- if page.url == child.url or page.parent == child.title and page.grand_parent == child.parent -%}
+              {%- assign second_level_url = child.url | absolute_url -%}
+            {%- endif -%}
+          {%- endif -%}
+        {%- endfor -%}
+      {%- endif -%}
+    {%- endif -%}
+  {%- endfor -%}
+
+  {% if page.has_children == true and page.has_toc != false %}
+    {%- assign toc_list = pages_list | where: "parent", page.title | where: "grand_parent", page.parent -%}
+  {%- endif -%}
+
+{%- endif -%}

_layouts/default.html

@@ -38,13 +38,6 @@ layout: table_wrappers
         <path d="M13 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V9z"></path><polyline points="13 2 13 9 20 9"></polyline>
       </svg>
     </symbol>
-    <symbol id="external-arrow" viewBox="0 0 16 16">
-      <title>External</title>
-      <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" viewBox="0 0 16 16">
-        <path fill-rule="evenodd" d="M8.636 3.5a.5.5 0 0 0-.5-.5H1.5A1.5 1.5 0 0 0 0 4.5v10A1.5 1.5 0 0 0 1.5 16h10a1.5 1.5 0 0 0 1.5-1.5V7.864a.5.5 0 0 0-1 0V14.5a.5.5 0 0 1-.5.5h-10a.5.5 0 0 1-.5-.5v-10a.5.5 0 0 1 .5-.5h6.636a.5.5 0 0 0 .5-.5z"/>
-        <path fill-rule="evenodd" d="M16 .5a.5.5 0 0 0-.5-.5h-5a.5.5 0 0 0 0 1h3.793L6.146 9.146a.5.5 0 1 0 .708.708L15 1.707V5.5a.5.5 0 0 0 1 0v-5z"/>
-      </svg>
-    </symbol>
   </svg>
 
   <div class="side-bar">
@@ -55,6 +48,14 @@ layout: table_wrappers
       </a>
     </div>
     <nav role="navigation" aria-label="Main" id="site-nav" class="site-nav">
+      {% assign pages_top_size = site.html_pages
+          | where_exp:"item", "item.title != nil"
+          | where_exp:"item", "item.parent == nil"
+          | where_exp:"item", "item.nav_exclude != true"
+          | size %}
+      {% if pages_top_size > 0 %}
+        {% include nav.html pages=site.html_pages key=nil %}
+      {% endif %}
       {% if site.just_the_docs.collections %}
         {% assign collections_size = site.just_the_docs.collections | size %}
         {% for collection_entry in site.just_the_docs.collections %}
@@ -62,19 +63,31 @@ layout: table_wrappers
           {% assign collection_value = collection_entry[1] %}
           {% assign collection = site[collection_key] %}
           {% if collection_value.nav_exclude != true %}
-            {% if collections_size > 1 %}
-              <div class="nav-category">{{ collection_value.name }}</div>
+            {% if collections_size > 1 or pages_top_size > 0 %}
+              {% if collection_value.nav_fold == true %}
+                <ul class="nav-list nav-category-list">
+                  <li class="nav-list-item{% if page.collection == collection_key %} active{% endif %}">
+                    {%- if collection.size > 0 -%}
+                    <a href="#" class="nav-list-expander"><svg viewBox="0 0 24 24"><use xlink:href="#svg-arrow-right"></use></svg></a>
+                    {%- endif -%}
+                    <div class="nav-category">{{ collection_value.name }}</div>
+                    {% include nav.html pages=collection key=collection_key %}
+                  </li>
+                </ul>
+              {% else %}
+                <div class="nav-category">{{ collection_value.name }}</div>
+                {% include nav.html pages=collection key=collection_key %}
+              {% endif %}
+            {% else %}
+              {% include nav.html pages=collection key=collection_key %}
             {% endif %}
-            {% include nav.html pages=collection %}
           {% endif %}
         {% endfor %}
-      {% else %}
-        {% include nav.html pages=site.html_pages %}
       {% endif %}
     </nav>
     <footer class="site-footer">
-      <p class="text-small text-grey-dk-100">See a problem? Submit <a href="https://github.com/opensearch-project/documentation-website/issues">issues</a> or <a href="https://github.com/opensearch-project/documentation-website/edit/main/{{ page.path }}">edit this page</a> on GitHub.</p>
-      <p class="text-small text-grey-dk-100 mb-0">© Amazon Web Services, Inc. or its affiliates. All rights reserved.</p>
+      <p class="text-small text-grey-dk-100">See a problem? Submit <a href="https://github.com/opensearch-project/documentation-website/issues">issues</a> or <a href="https://github.com/opensearch-project/documentation-website/edit/main/{{ page.path }}">edit this page</a> on <a href="https://github.com/opensearch-project/documentation-website/">GitHub</a>.</p>
+      <p class="text-small text-grey-dk-100 mb-0">© 2021 OpenSearch contributors. This documentation is under the Apache License 2.0.</p>
     </footer>
   </div>
   <div class="main" id="top">
@@ -110,21 +123,6 @@ layout: table_wrappers
     <div id="main-content-wrap" class="main-content-wrap">
       {% unless page.url == "/" %}
         {% if page.parent %}
-          {%- for node in pages_list -%}
-            {%- if node.parent == nil -%}
-              {%- if page.parent == node.title or page.grand_parent == node.title -%}
-                {%- assign first_level_url = node.url | absolute_url -%}
-              {%- endif -%}
-              {%- if node.has_children -%}
-                {%- assign children_list = pages_list | where: "parent", node.title -%}
-                {%- for child in children_list -%}
-                  {%- if page.url == child.url or page.parent == child.title -%}
-                    {%- assign second_level_url = child.url | absolute_url -%}
-                  {%- endif -%}
-                {%- endfor -%}
-              {%- endif -%}
-            {%- endif -%}
-          {%- endfor -%}
           <nav aria-label="Breadcrumb" class="breadcrumb-nav">
             <ol class="breadcrumb-nav-list">
               {% if page.grand_parent %}
@@ -142,7 +140,7 @@ layout: table_wrappers
         {% if site.heading_anchors != false %}
           {% include vendor/anchor_headings.html html=content beforeHeading="true" anchorBody="<svg viewBox=\"0 0 16 16\" aria-hidden=\"true\"><use xlink:href=\"#svg-link\"></use></svg>" anchorClass="anchor-heading" anchorAttrs="aria-labelledby=\"%html_id%\"" %}
         {% else %}
-          <p class="warning" style="margin-top: 0">Like OpenSearch itself, this documentation is a beta. It has content gaps and might contain bugs.</p>
+          <p class="warning" style="margin-top: 0">This documentation remains in a beta state. It has content gaps and might contain bugs.</p>
           {{ content }}
         {% endif %}
 
@@ -150,8 +148,7 @@ layout: table_wrappers
           <hr>
           <h2 class="text-delta">Table of contents</h2>
           <ul>
-            {%- assign children_list = pages_list | where: "parent", page.title | where: "grand_parent", page.parent -%}
-            {% for child in children_list %}
+            {% for child in toc_list %}
               <li>
                 <a href="{{ child.url | absolute_url }}">{{ child.title }}</a>{% if child.summary %} - {{ child.summary }}{% endif %}
               </li>

_monitoring-plugins/ad/api.md

@@ -28,7 +28,7 @@ This command creates a detector named `http_requests` that finds anomalies based
 #### Request
 
 ```json
-POST _opensearch/_anomaly_detection/detectors
+POST _plugins/_anomaly_detection/detectors
 {
   "name": "test-detector",
   "description": "Test detector",
@@ -143,7 +143,7 @@ To set a category field for high cardinality:
 #### Request
 
 ```json
-POST _opensearch/_anomaly_detection/detectors
+POST _plugins/_anomaly_detection/detectors
 {
   "name": "Host OK Rate Detector",
   "description": "ok rate",
@@ -243,7 +243,7 @@ To create a historical detector:
 #### Request
 
 ```json
-POST _opensearch/_anomaly_detection/detectors
+POST _plugins/_anomaly_detection/detectors
 {
   "name": "test1",
   "description": "test historical detector",
@@ -312,7 +312,7 @@ Passes a date range to the anomaly detector to return any anomalies within that
 #### Request
 
 ```json
-POST _opensearch/_anomaly_detection/detectors/<detectorId>/_preview
+POST _plugins/_anomaly_detection/detectors/<detectorId>/_preview
 {
   "period_start": 1588838250000,
   "period_end": 1589443050000
@@ -452,7 +452,7 @@ Starts a real-time or historical anomaly detector job.
 #### Request
 
 ```json
-POST _opensearch/_anomaly_detection/detectors/<detectorId>/_start
+POST _plugins/_anomaly_detection/detectors/<detectorId>/_start
 ```
 
 #### Sample response
@@ -476,7 +476,7 @@ Stops a real-time or historical anomaly detector job.
 #### Request
 
 ```json
-POST _opensearch/_anomaly_detection/detectors/<detectorId>/_stop
+POST _plugins/_anomaly_detection/detectors/<detectorId>/_stop
 ```
 
 #### Sample response
@@ -494,8 +494,8 @@ Returns all results for a search query.
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/results/_search
-POST _opensearch/_anomaly_detection/detectors/results/_search
+GET _plugins/_anomaly_detection/detectors/results/_search
+POST _plugins/_anomaly_detection/detectors/results/_search
 
 {
   "query": {
@@ -596,7 +596,7 @@ To see an ordered set of anomaly records for an entity with an anomaly within a
 #### Request
 
 ```json
-POST _opensearch/_anomaly_detection/detectors/results/_search
+POST _plugins/_anomaly_detection/detectors/results/_search
 {
   "query": {
     "bool": {
@@ -782,7 +782,7 @@ To get the latest task:
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/<detector_id>?task=true
+GET _plugins/_anomaly_detection/detectors/<detector_id>?task=true
 ```
 
 To query the anomaly results with `task_id`:
@@ -790,7 +790,7 @@ To query the anomaly results with `task_id`:
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/results/_search
+GET _plugins/_anomaly_detection/detectors/results/_search
 {
   "query": {
     "term": {
@@ -940,7 +940,7 @@ To delete a detector, you need to first stop the detector.
 #### Request
 
 ```json
-DELETE _opensearch/_anomaly_detection/detectors/<detectorId>
+DELETE _plugins/_anomaly_detection/detectors/<detectorId>
 ```
 
 
@@ -975,7 +975,7 @@ To update a detector, you need to first stop the detector.
 #### Request
 
 ```json
-PUT _opensearch/_anomaly_detection/detectors/<detectorId>
+PUT _plugins/_anomaly_detection/detectors/<detectorId>
 {
   "name": "test-detector",
   "description": "Test detector",
@@ -1091,7 +1091,7 @@ To update a historical detector:
 #### Request
 
 ```json
-PUT _opensearch/_anomaly_detection/detectors/<detectorId>
+PUT _plugins/_anomaly_detection/detectors/<detectorId>
 {
   "name": "test1",
   "description": "test historical detector",
@@ -1145,7 +1145,7 @@ Returns all information about a detector based on the `detector_id`.
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/<detectorId>
+GET _plugins/_anomaly_detection/detectors/<detectorId>
 ```
 
 #### Sample response
@@ -1215,7 +1215,7 @@ Use `job=true` to get anomaly detection job information.
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/<detectorId>?job=true
+GET _plugins/_anomaly_detection/detectors/<detectorId>?job=true
 ```
 
 #### Sample response
@@ -1304,7 +1304,7 @@ Use `task=true` to get historical detector task information.
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/<detectorId>?task=true
+GET _plugins/_anomaly_detection/detectors/<detectorId>?task=true
 ```
 
 #### Sample response
@@ -1491,8 +1491,8 @@ Returns all anomaly detectors for a search query.
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/_search
-POST _opensearch/_anomaly_detection/detectors/_search
+GET _plugins/_anomaly_detection/detectors/_search
+POST _plugins/_anomaly_detection/detectors/_search
 
 Sample Input:
 {
@@ -1597,10 +1597,10 @@ Provides information about how the plugin is performing.
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/stats
-GET _opensearch/_anomaly_detection/<nodeId>/stats
-GET _opensearch/_anomaly_detection/<nodeId>/stats/<stat>
-GET _opensearch/_anomaly_detection/stats/<stat>
+GET _plugins/_anomaly_detection/stats
+GET _plugins/_anomaly_detection/<nodeId>/stats
+GET _plugins/_anomaly_detection/<nodeId>/stats/<stat>
+GET _plugins/_anomaly_detection/stats/<stat>
 ```
 
 #### Sample response
@@ -1697,7 +1697,7 @@ Create a monitor to set up alerts for the detector.
 #### Request
 
 ```json
-POST _opensearch/_alerting/monitors
+POST _plugins/_alerting/monitors
 {
   "type": "monitor",
   "name": "test-monitor",
@@ -1919,23 +1919,23 @@ It also helps track the initialization percentage, the required shingles, and th
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile/
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile?_all=true
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile/<type>
-GET /_opensearch/_anomaly_detection/detectors/<detectorId>/_profile/<type1>,<type2>
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile/
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile?_all=true
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile/<type>
+GET /_plugins/_anomaly_detection/detectors/<detectorId>/_profile/<type1>,<type2>
 ```
 
 #### Sample Responses
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile
 
 {
     "state":"DISABLED",
     "error":"Stopped detector: AD models memory usage exceeds our limit."
 }
 
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile?_all=true&pretty
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile?_all=true&pretty
 
 {
   "state": "RUNNING",
@@ -1970,7 +1970,7 @@ GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile?_all=true&pre
   }
 }
 
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile/total_size_in_bytes
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile/total_size_in_bytes
 
 {
   "total_size_in_bytes" : 13369344
@@ -1984,7 +1984,7 @@ You can use this data to estimate how much memory is required for anomaly detect
 #### Request
 
 ```json
-GET /_opensearch/_anomaly_detection/detectors/<detectorId>/_profile?_all=true&pretty
+GET /_plugins/_anomaly_detection/detectors/<detectorId>/_profile?_all=true&pretty
 
 {
   "state": "RUNNING",
@@ -2043,7 +2043,7 @@ If there are no anomaly results for an entity, either the entity doesn't have an
 #### Request
 
 ```json
-GET /_opensearch/_anomaly_detection/detectors/<detectorId>/_profile?_all=true&entity=i-00f28ec1eb8997686
+GET /_plugins/_anomaly_detection/detectors/<detectorId>/_profile?_all=true&entity=i-00f28ec1eb8997686
 {
   "category_field": "host",
   "value": "i-00f28ec1eb8997686",
@@ -2067,8 +2067,8 @@ For a historical detector, specify `_all` or `ad_task` to see information about
 #### Request
 
 ```json
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile?_all
-GET _opensearch/_anomaly_detection/detectors/<detectorId>/_profile/ad_task
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile?_all
+GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile/ad_task
 ```
 
 #### Sample Responses

_monitoring-plugins/ad/index.md

@@ -3,6 +3,8 @@ layout: default
 title: Anomaly detection
 nav_order: 46
 has_children: true
+redirect_from:
+  - /monitoring-plugins/ad/
 ---
 
 # Anomaly detection
@@ -13,7 +15,7 @@ It can be challenging to discover anomalies using conventional methods such as c
 
 Anomaly detection  automatically detects anomalies in your OpenSearch data in near real-time using the Random Cut Forest (RCF) algorithm. RCF is an unsupervised machine learning algorithm that models a sketch of your incoming data stream to compute an `anomaly grade` and `confidence score` value for each incoming data point. These values are used to differentiate an anomaly from normal variations. For more information about how RCF works, see [Random Cut Forests](https://pdfs.semanticscholar.org/8bba/52e9797f2e2cc9a823dbd12514d02f29c8b9.pdf?_ga=2.56302955.1913766445.1574109076-1059151610.1574109076).
 
-You can pair the anomaly detection plugin with the [alerting plugin](../alerting/) to notify you as soon as an anomaly is detected.
+You can pair the anomaly detection plugin with the [alerting plugin]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/) to notify you as soon as an anomaly is detected.
 
 To use the anomaly detection plugin, your computer needs to have more than one CPU core.
 {: .note }
@@ -52,7 +54,7 @@ A feature is the field in your index that you want to check for anomalies. A det
 
 For example, if you choose `min()`, the detector focuses on finding anomalies based on the minimum values of your feature. If you choose `average()`, the detector finds anomalies based on the average values of your feature.
 
-A multi-feature model correlates anomalies across all its features. The [curse of dimensionality](https://en.wikipedia.org/wiki/Curse_of_dimensionality) makes it less likely for multi-feature models to identify smaller anomalies as compared to a single-feature model. Adding more features might negatively impact the [precision and recall](https://en.wikipedia.org/wiki/Precision_and_recall) of a model. A higher proportion of noise in your data might further amplify this negative impact. Selecting the optimal feature set is usually an iterative process. We recommend experimenting with a historical detector with different feature sets and checking the precision before moving on to real-time detectors. By default, the maximum number of features for a detector is 5. You can adjust this limit with the `opendistro.anomaly_detection.max_anomaly_features` setting.
+A multi-feature model correlates anomalies across all its features. The [curse of dimensionality](https://en.wikipedia.org/wiki/Curse_of_dimensionality) makes it less likely for multi-feature models to identify smaller anomalies as compared to a single-feature model. Adding more features might negatively impact the [precision and recall](https://en.wikipedia.org/wiki/Precision_and_recall) of a model. A higher proportion of noise in your data might further amplify this negative impact. Selecting the optimal feature set is usually an iterative process. We recommend experimenting with a historical detector with different feature sets and checking the precision before moving on to real-time detectors. By default, the maximum number of features for a detector is 5. You can adjust this limit with the `plugins.anomaly_detection.max_anomaly_features` setting.
 {: .note }
 
 1. On the **Model configuration** page, enter the **Feature name**.
@@ -100,11 +102,11 @@ Examine the sample preview and use it to fine-tune your feature configurations (
 Choose the **Anomaly results** tab. You need to wait for some time to see the anomaly results. If the detector interval is 10 minutes, the detector might take more than an hour to start, as it's waiting for sufficient data to generate anomalies.
 
 A shorter interval means the model passes the shingle process more quickly and starts to generate the anomaly results sooner.
-Use the [profile detector](./api#profile-detector) operation to make sure you have sufficient data points.
+Use the [profile detector]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/api#profile-detector) operation to make sure you have sufficient data points.
 
 If you see the detector pending in "initialization" for longer than a day, aggregate your existing data using the detector interval to check for any missing data points. If you find a lot of missing data points from the aggregated data, consider increasing the detector interval.
 
-![Anomaly detection results](../images/ad.png)
+![Anomaly detection results]({{site.url}}{{site.baseurl}}/images/ad.png)
 
 Analize anomalies with the following visualizations:
 
@@ -113,7 +115,7 @@ Analize anomalies with the following visualizations:
 - **Feature breakdown** - plots the features based on the aggregation method. You can vary the date-time range of the detector.
 - **Anomaly occurrence** - shows the `Start time`, `End time`, `Data confidence`, and `Anomaly grade` for each detected anomaly.
 
-`Anomaly grade` is a number between 0 and 1 that indicates how anomalous a data point is. An anomaly grade of 0 represents “not an anomaly,” and a non-zero value represents the relative severity of the anomaly. 
+`Anomaly grade` is a number between 0 and 1 that indicates how anomalous a data point is. An anomaly grade of 0 represents “not an anomaly,” and a non-zero value represents the relative severity of the anomaly.
 
 `Data confidence` is an estimate of the probability that the reported anomaly grade matches the expected anomaly grade. Confidence increases as the model observes more data and learns the data behavior and trends. Note that confidence is distinct from model accuracy.
 
@@ -124,7 +126,7 @@ Choose a filled rectangle to see a more detailed view of the anomaly.
 
 ### Step 4: Set up alerts
 
-Choose **Set up alerts** and configure a monitor to notify you when anomalies are detected. For steps to create a monitor and set up notifications based on your anomaly detector, see [Monitors](../alerting/monitors/).
+Choose **Set up alerts** and configure a monitor to notify you when anomalies are detected. For steps to create a monitor and set up notifications based on your anomaly detector, see [Monitors]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/monitors/).
 
 If you stop or delete a detector, make sure to delete any monitors associated with it.
 

_monitoring-plugins/ad/security.md

@@ -10,24 +10,24 @@ has_children: false
 
 You can use the security plugin with anomaly detection in OpenSearch to limit non-admin users to specific actions. For example, you might want some users to only be able to create, update, or delete detectors, while others to only view detectors.
 
-All anomaly detection indices are protected as system indices. Only a super admin user or an admin user with a TLS certificate can access system indices. For more information, see [System indices](../../security/configuration/system-indices/).
+All anomaly detection indices are protected as system indices. Only a super admin user or an admin user with a TLS certificate can access system indices. For more information, see [System indices]({{site.url}}{{site.baseurl}}/security-plugin/configuration/system-indices/).
 
 
-Security for anomaly detection works the same as [security for alerting](../../alerting/security/).
+Security for anomaly detection works the same as [security for alerting]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/security/).
 
 ## Basic permissions
 
-As an admin user, you can use the security plugin to assign specific permissions to users based on which APIs they need access to. For a list of supported APIs, see [Anomaly detection API](../api/).
+As an admin user, you can use the security plugin to assign specific permissions to users based on which APIs they need access to. For a list of supported APIs, see [Anomaly detection API]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/api/).
 
-The security plugin has two built-in roles that cover most anomaly detection use cases: `anomaly_full_access` and `anomaly_read_access`. For descriptions of each, see [Predefined roles](../../security/access-control/users-roles/#predefined-roles).
+The security plugin has two built-in roles that cover most anomaly detection use cases: `anomaly_full_access` and `anomaly_read_access`. For descriptions of each, see [Predefined roles]({{site.url}}{{site.baseurl}}/security-plugin/access-control/users-roles#predefined-roles).
 
-If these roles don't meet your needs, mix and match individual anomaly detection [permissions](../../security/access-control/permissions/) to suit your use case. Each action corresponds to an operation in the REST API. For example, the `cluster:admin/opensearch/ad/detector/delete` permission lets you delete detectors.
+If these roles don't meet your needs, mix and match individual anomaly detection [permissions]({{site.url}}{{site.baseurl}}/security-plugin/access-control/permissions/) to suit your use case. Each action corresponds to an operation in the REST API. For example, the `cluster:admin/opensearch/ad/detector/delete` permission lets you delete detectors.
 
 ## (Advanced) Limit access by backend role
 
 Use backend roles to configure fine-grained access to individual detectors based on roles. For example, users of different departments in an organization can view detectors owned by their own department.
 
-First, make sure your users have the appropriate [backend roles](../../security/access-control/). Backend roles usually come from an [LDAP server](../../security/configuration/ldap/) or [SAML provider](../../security/configuration/saml/), but if you use the internal user database, you can use the REST API to [add them manually](../../security/access-control/api/#create-user).
+First, make sure your users have the appropriate [backend roles]({{site.url}}{{site.baseurl}}/security-plugin/access-control/index/). Backend roles usually come from an [LDAP server]({{site.url}}{{site.baseurl}}/security-plugin/configuration/ldap/) or [SAML provider]({{site.url}}{{site.baseurl}}/security-plugin/configuration/saml/), but if you use the internal user database, you can use the REST API to [add them manually]({{site.url}}{{site.baseurl}}/security-plugin/access-control/api#create-user).
 
 Next, enable the following setting:
 
@@ -35,7 +35,7 @@ Next, enable the following setting:
 PUT _cluster/settings
 {
   "transient": {
-    "opendistro.anomaly_detection.filter_by_backend_roles": "true"
+    "plugins.anomaly_detection.filter_by_backend_roles": "true"
   }
 }
 ```
@@ -46,7 +46,7 @@ For example, consider two users: `alice` and `bob`.
 `alice` has an analyst backend role:
 
 ```json
-PUT _opensearch/_security/api/internalusers/alice
+PUT _plugins/_security/api/internalusers/alice
 {
   "password": "alice",
   "backend_roles": [
@@ -59,7 +59,7 @@ PUT _opensearch/_security/api/internalusers/alice
 `bob` has a human-resources backend role:
 
 ```json
-PUT _opensearch/_security/api/internalusers/bob
+PUT _plugins/_security/api/internalusers/bob
 {
   "password": "bob",
   "backend_roles": [
@@ -72,7 +72,7 @@ PUT _opensearch/_security/api/internalusers/bob
 Both `alice` and `bob` have full access to anomaly detection:
 
 ```json
-PUT _opensearch/_security/api/rolesmapping/anomaly_full_access
+PUT _plugins/_security/api/rolesmapping/anomaly_full_access
 {
   "backend_roles": [],
   "hosts": [],

_monitoring-plugins/ad/settings.md

@@ -0,0 +1,42 @@
+---
+layout: default
+title: Settings
+parent: Anomaly detection
+nav_order: 4
+---
+
+# Settings
+
+The anomaly detection plugin adds several settings to the standard OpenSearch cluster settings.
+The settings are dynamic, so you can change the default behavior of the plugin without restarting your cluster.
+You can mark settings as `persistent` or `transient`.
+
+For example, to update the retention period of the result index:
+
+```json
+PUT _cluster/settings
+{
+  "transient": {
+    "plugins.anomaly_detection.ad_result_history_retention_period": "5m"
+  }
+}
+```
+
+Setting | Default | Description
+:--- | :--- | :---
+`plugins.anomaly_detection.enabled` | True | Whether the anomaly detection plugin is enabled or not. If disabled, all detectors immediately stop running.
+`plugins.anomaly_detection.max_anomaly_detectors` | 1,000 | The maximum number of non-high cardinality detectors (no category field) users can create.
+`plugins.anomaly_detection.max_multi_entity_anomaly_detectors` | 10 | The maximum number of high cardinality detectors (with category field) in a cluster.
+`plugins.anomaly_detection.max_anomaly_features` | 5 | The maximum number of features for a detector.
+`plugins.anomaly_detection.ad_result_history_rollover_period` | 12h | How often the rollover condition is checked. If `true`, the plugin rolls over the result index to a new index.
+`plugins.anomaly_detection.ad_result_history_max_docs` | 250000000 | The maximum number of documents in one result index. The plugin only counts refreshed documents in the primary shards.
+`plugins.anomaly_detection.ad_result_history_retention_period` | 30d | The maximum age of the result index.  If its age exceeds the threshold, the plugin deletes the rolled over result index. If the cluster has only one result index, the plugin keeps the index even if it's older than its configured retention period.
+`plugins.anomaly_detection.max_entities_per_query` | 1,000 | The maximum unique values per detection interval for high cardinality detectors. By default, if the category field has more than 1,000 unique values in a detector interval, the plugin selects the top 1,000 values and orders them by `doc_count`.
+`plugins.anomaly_detection.max_entities_for_preview` | 30 | The maximum unique category field values displayed with the preview operation for high cardinality detectors. If the category field has more than 30 unique values, the plugin selects the top 30 values and orders them by `doc_count`.
+`plugins.anomaly_detection.max_primary_shards` | 10 | The maximum number of primary shards an anomaly detection index can have.
+`plugins.anomaly_detection.filter_by_backend_roles` | False | When you enable the security plugin and set this to `true`, the plugin filters results based on the user's backend role(s).
+`plugins.anomaly_detection.max_cache_miss_handling_per_second` | 100 | High cardinality detectors use a cache to store active models. In the event of a cache miss, the cache gets the models from the model checkpoint index. Use this setting to limit the rate of fetching models. Because the thread pool for a GET operation has a queue of 1,000, we recommend setting this value below 1,000.
+`plugins.anomaly_detection.max_batch_task_per_node` | 2 | Starting a historical detector triggers a batch task. This setting is the number of batch tasks that you can run per data node. You can tune this setting from 1 to 1000. If the data nodes can't support all batch tasks and you're not sure if the data nodes are capable of running more historical detectors, add more data nodes instead of changing this setting to a higher value.
+`plugins.anomaly_detection.max_old_ad_task_docs_per_detector` | 10 | You can run the same historical detector many times. For each run, the anomaly detection plugin creates a new task. This setting is the number of previous tasks the plugin keeps. Set this value to at least 1 to track its last run. You can keep a maximum of 1,000 old tasks to avoid overwhelming the cluster.
+`plugins.anomaly_detection.batch_task_piece_size` | 1000 | The date range for a historical task is split into smaller pieces and the anomaly detection plugin runs the task piece by piece. Each piece contains 1,000 detection intervals by default. For example, if detector interval is 1 minute and one piece is 1000 minutes, the feature data is queried every 1,000 minutes. You can change this setting from 1 to 10,000.
+`plugins.anomaly_detection.batch_task_piece_interval_seconds` | 5 | Add a time interval between historical detector tasks. This interval prevents the task from consuming too much of the available resources and starving other operations like search and bulk index. You can change this setting from 1 to 600 seconds.

_monitoring-plugins/alerting/api.md

@@ -24,7 +24,7 @@ Use the alerting API to programmatically manage monitors and alerts.
 #### Request
 
 ```json
-POST _opensearch/_alerting/monitors
+POST _plugins/_alerting/monitors
 {
   "type": "monitor",
   "name": "test-monitor",
@@ -174,7 +174,7 @@ If you use a custom webhook for your destination and need to embed JSON in the m
 }
 ```
 
-If you want to specify a timezone, you can do so by including a [cron expression](../cron/) with a timezone name in the `schedule` section of your request.
+If you want to specify a timezone, you can do so by including a [cron expression]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/cron/) with a timezone name in the `schedule` section of your request.
 
 The following example creates a monitor that runs at 12:10 PM Pacific Time on the 1st day of every month.
 
@@ -252,7 +252,7 @@ When you update a monitor, include the current version number as a parameter. Op
 #### Request
 
 ```json
-PUT _opensearch/_alerting/monitors/<monitor_id>
+PUT _plugins/_alerting/monitors/<monitor_id>
 {
   "type": "monitor",
   "name": "test-monitor",
@@ -372,7 +372,7 @@ PUT _opensearch/_alerting/monitors/<monitor_id>
 #### Request
 
 ```
-GET _opensearch/_alerting/monitors/<monitor_id>
+GET _plugins/_alerting/monitors/<monitor_id>
 ```
 
 #### Sample response
@@ -439,15 +439,15 @@ GET _opensearch/_alerting/monitors/<monitor_id>
 
 ## Monitor stats
 
-Returns statistics about the alerting feature. Use `_opensearch/_alerting/stats` to find node IDs and metrics. Then you can drill down using those values.
+Returns statistics about the alerting feature. Use `_plugins/_alerting/stats` to find node IDs and metrics. Then you can drill down using those values.
 
 #### Request
 
 ```json
-GET _opensearch/_alerting/stats
-GET _opensearch/_alerting/stats/<metric>
-GET _opensearch/_alerting/<node-id>/stats
-GET _opensearch/_alerting/<node-id>/stats/<metric>
+GET _plugins/_alerting/stats
+GET _plugins/_alerting/stats/<metric>
+GET _plugins/_alerting/<node-id>/stats
+GET _plugins/_alerting/<node-id>/stats/<metric>
 ```
 
 #### Sample response
@@ -460,7 +460,7 @@ GET _opensearch/_alerting/<node-id>/stats/<metric>
     "failed": 0
   },
   "cluster_name": "475300751431:alerting65-dont-delete",
-  "opensearch.scheduled_jobs.enabled": true,
+  "plugins.scheduled_jobs.enabled": true,
   "scheduled_job_index_exists": true,
   "scheduled_job_index_status": "green",
   "nodes_on_schedule": 9,
@@ -631,7 +631,7 @@ GET _opensearch/_alerting/<node-id>/stats/<metric>
 #### Request
 
 ```
-DELETE _opensearch/_alerting/monitors/<monitor_id>
+DELETE _plugins/_alerting/monitors/<monitor_id>
 ```
 
 #### Sample response
@@ -662,7 +662,7 @@ DELETE _opensearch/_alerting/monitors/<monitor_id>
 #### Request
 
 ```json
-GET _opensearch/_alerting/monitors/_search
+GET _plugins/_alerting/monitors/_search
 {
   "query": {
     "match" : {
@@ -762,7 +762,7 @@ You can add the optional `?dryrun=true` parameter to the URL to show the results
 #### Request
 
 ```json
-POST _opensearch/_alerting/monitors/<monitor_id>/_execute
+POST _plugins/_alerting/monitors/<monitor_id>/_execute
 ```
 
 #### Sample response
@@ -793,7 +793,7 @@ Returns an array of all alerts.
 #### Request
 
 ```json
-GET _opensearch/_alerting/monitors/alerts
+GET _plugins/_alerting/monitors/alerts
 ```
 
 #### Response
@@ -862,7 +862,7 @@ GET _opensearch/_alerting/monitors/alerts
 #### Request
 
 ```json
-POST _opensearch/_alerting/monitors/<monitor-id>/_acknowledge/alerts
+POST _plugins/_alerting/monitors/<monitor-id>/_acknowledge/alerts
 {
   "alerts": ["eQURa3gBKo1jAh6qUo49"]
 }
@@ -886,7 +886,7 @@ POST _opensearch/_alerting/monitors/<monitor-id>/_acknowledge/alerts
 #### Requests
 
 ```json
-POST _opensearch/_alerting/destinations
+POST _plugins/_alerting/destinations
 {
   "name": "my-destination",
   "type": "slack",
@@ -895,7 +895,7 @@ POST _opensearch/_alerting/destinations
   }
 }
 
-POST _opensearch/_alerting/destinations
+POST _plugins/_alerting/destinations
 {
   "type": "custom_webhook",
   "name": "my-custom-destination",
@@ -912,6 +912,27 @@ POST _opensearch/_alerting/destinations
     "host": "hooks.chime.aws"
   }
 }
+
+POST _plugins/_alerting/destinations
+{
+  "type": "email",
+  "name": "my-email-destination",
+  "email": {
+    "email_account_id": "YjY7mXMBx015759_IcfW",
+    "recipients": [
+      {
+        "type": "email_group",
+        "email_group_id": "YzY-mXMBx015759_dscs"
+      },
+      {
+        "type": "email",
+        "email": "example@email.com"
+      }
+    ]
+  }
+}
+
+// The email_account_id and email_group_id will be the document IDs of the email_account and email_group you have created.
 ```
 
 #### Sample response
@@ -939,7 +960,7 @@ POST _opensearch/_alerting/destinations
 #### Request
 
 ```json
-PUT _opensearch/_alerting/destinations/<destination-id>
+PUT _plugins/_alerting/destinations/<destination-id>
 {
   "name": "my-updated-destination",
   "type": "slack",
@@ -976,7 +997,7 @@ Retrieve one destination.
 #### Requests
 
 ```json
-GET _opensearch/_alerting/destinations/<destination-id>
+GET _plugins/_alerting/destinations/<destination-id>
 ```
 
 #### Sample response
@@ -1021,7 +1042,7 @@ Retrieve all destinations.
 #### Requests
 
 ```json
-GET _opensearch/_alerting/destinations
+GET _plugins/_alerting/destinations
 ```
 
 #### Sample response
@@ -1064,7 +1085,7 @@ GET _opensearch/_alerting/destinations
 #### Request
 
 ```
-DELETE _opensearch/_alerting/destinations/<destination-id>
+DELETE _plugins/_alerting/destinations/<destination-id>
 ```
 
 #### Sample response
@@ -1092,7 +1113,7 @@ DELETE _opensearch/_alerting/destinations/<destination-id>
 
 #### Request
 ```json
-POST _opensearch/_alerting/destinations/email_accounts
+POST _plugins/_alerting/destinations/email_accounts
 {
   "name": "example_account",
   "email": "example@email.com",
@@ -1124,7 +1145,7 @@ POST _opensearch/_alerting/destinations/email_accounts
 
 #### Request
 ```json
-PUT _opensearch/_alerting/destinations/email_accounts/<email_account_id>
+PUT _plugins/_alerting/destinations/email_accounts/<email_account_id>
 {
   "name": "example_account",
   "email": "example@email.com",
@@ -1155,7 +1176,7 @@ PUT _opensearch/_alerting/destinations/email_accounts/<email_account_id>
 
 #### Request
 ```json
-GET _opensearch/_alerting/destinations/email_accounts/<email_account_id>
+GET _plugins/_alerting/destinations/email_accounts/<email_account_id>
 {
   "name": "example_account",
   "email": "example@email.com",
@@ -1186,7 +1207,7 @@ GET _opensearch/_alerting/destinations/email_accounts/<email_account_id>
 
 #### Request
 ```
-DELETE _opensearch/_alerting/destinations/email_accounts/<email_account_id>
+DELETE _plugins/_alerting/destinations/email_accounts/<email_account_id>
 ```
 #### Sample response
 
@@ -1213,7 +1234,7 @@ DELETE _opensearch/_alerting/destinations/email_accounts/<email_account_id>
 #### Request
 
 ```json
-POST _opensearch/_alerting/destinations/email_accounts/_search
+POST _plugins/_alerting/destinations/email_accounts/_search
 {
   "from": 0,
   "size": 20,
@@ -1279,7 +1300,7 @@ POST _opensearch/_alerting/destinations/email_accounts/_search
 #### Request
 
 ```json
-POST _opensearch/_alerting/destinations/email_groups
+POST _plugins/_alerting/destinations/email_groups
 {
   "name": "example_email_group",
   "emails": [{
@@ -1313,7 +1334,7 @@ POST _opensearch/_alerting/destinations/email_groups
 #### Request
 
 ```json
-PUT _opensearch/_alerting/destinations/email_groups/<email_group_id>
+PUT _plugins/_alerting/destinations/email_groups/<email_group_id>
 {
   "name": "example_email_group",
   "emails": [{
@@ -1345,7 +1366,7 @@ PUT _opensearch/_alerting/destinations/email_groups/<email_group_id>
 
 #### Request
 ```json
-GET _opensearch/_alerting/destinations/email_groups/<email_group_id>
+GET _plugins/_alerting/destinations/email_groups/<email_group_id>
 {
   "name": "example_email_group",
   "emails": [{
@@ -1377,7 +1398,7 @@ GET _opensearch/_alerting/destinations/email_groups/<email_group_id>
 
 #### Request
 ```
-DELETE _opensearch/_alerting/destinations/email_groups/<email_group_id>
+DELETE _plugins/_alerting/destinations/email_groups/<email_group_id>
 ```
 #### Sample response
 
@@ -1404,7 +1425,7 @@ DELETE _opensearch/_alerting/destinations/email_groups/<email_group_id>
 #### Request
 
 ```json
-POST _opensearch/_alerting/destinations/email_groups/_search
+POST _plugins/_alerting/destinations/email_groups/_search
 {
   "from": 0,
   "size": 20,

_monitoring-plugins/alerting/cron.md

@@ -4,6 +4,9 @@ title: Cron
 nav_order: 20
 parent: Alerting
 has_children: false
+redirect_from:
+  - /alerting/cron/
+  - /docs/alerting/cron/
 ---
 
 # Cron expression reference
@@ -61,4 +64,4 @@ Every three hours on the first day of every other month:
 
 ## API
 
-For an example of how to use a custom cron expression in an API call, see the [create monitor API operation](../api/#request-1).
+For an example of how to use a custom cron expression in an API call, see the [create monitor API operation]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/api#request-1).

_monitoring-plugins/alerting/index.md

@@ -3,6 +3,8 @@ layout: default
 title: Alerting
 nav_order: 34
 has_children: true
+redirect_from:
+  - /monitoring-plugins/alerting/
 ---
 
 # Alerting
@@ -13,4 +15,4 @@ The alerting feature notifies you when data from one or more OpenSearch indices
 
 To get started, choose **Alerting** in OpenSearch Dashboards.
 
-![OpenSearch Dashboards side bar with link](../images/alerting.png)
+![OpenSearch Dashboards side bar with link]({{site.url}}{{site.baseurl}}/images/alerting.png)

_monitoring-plugins/alerting/monitors.md

@@ -32,68 +32,14 @@ Destination | A reusable location for an action, such as Amazon Chime, Slack, or
 
 1. Choose **Alerting**, **Destinations**, **Add destination**.
 1. Specify a name for the destination so that you can identify it later.
-1. For **Type**, choose Slack, Amazon Chime, Amazon Simple Notification Service (SNS), custom webhook, or [email](#email-as-a-destination).
+1. For **Type**, choose Slack, Amazon Chime, custom webhook, or [email](#email-as-a-destination).
 
-For more information about Amazon SNS or email type, refer to their respective sections below. For Amazon Chime, Slack, or custom webhook, specify the webhook URL. For more information about webhooks, see the documentation for [Slack](https://api.slack.com/incoming-webhooks) and [Chime](https://docs.aws.amazon.com/chime/latest/ug/webhooks.html).
+For Email type, refer to [Email as a destination](#email-as-a-destination) section below. For all other types, specify the webhook URL. For more information about webhooks, see the documentation for [Slack](https://api.slack.com/incoming-webhooks) and [Chime](https://docs.aws.amazon.com/chime/latest/ug/webhooks.html).
 
 For custom webhooks, you must specify more information: parameters and headers. For example, if your endpoint requires basic authentication, you might need to add a header with a key of `Authorization` and a value of `Basic <Base64-encoded-credential-string>`. You might also need to change `Content-Type` to whatever your webhook requires. Popular values are `application/json`, `application/xml`, and `text/plain`.
 
 This information is stored in plain text in the OpenSearch cluster. We will improve this design in the future, but for now, the encoded credentials (which are neither encrypted nor hashed) might be visible to other OpenSearch users.
 
-### Amazon SNS as a destination
-
-OpenSearch supports Amazon SNS for notifications. This integration with Amazon SNS means that, in addition to the other destinations, the alerting plugin can send emails, text messages, and even run AWS Lambda functions using SNS topics. For more information about Amazon SNS, see the [Amazon Simple Notification Service Developer Guide](https://docs.aws.amazon.com/sns/latest/dg/welcome.html).
-
-To use Amazon SNS as a destination:
-
-1. Enter a unique name for your destination.
-1. For **destination type**, choose **Amazon SNS**.
-1. Specify the SNS topic ARN that you want to use.
-
-The alerting plugin currently supports user authentication through OpenSearch's keystore and IAM in Amazon Web Services. If you run your OpenSearch cluster on AWS infrastructure (an Amazon EC2 instance), the alerting plugin automatically retrieves the credentials of an IAM role associated with your EC2 instance. If you're not running your cluster on Amazon EC2, you must add your IAM user's access key and secret key to OpenSearch's keystore.
-
-To use either method, first ensure that the IAM role you want to use has the following trust relationship and permissions:
-
-```json
-{
-  "Version": "2012-10-17",
-  "Statement": [{
-    "Effect": "Allow",
-    "Principal": {
-      "Service": "ec2.amazonaws.com"
-    },
-    "Action": "sts:AssumeRole"
-  }]
-}
-```
-
-```json
-{
-  "Version": "2012-10-17",
-  "Statement": [{
-    "Effect": "Allow",
-    "Action": "sns:Publish",
-    "Resource": "sns-topic-arn"
-  }]
-}
-```
-
-#### Using an IAM role's credentials
-
-If you're running your OpenSearch cluster on AWS infrastructure, Amazon EC2 will automatically retrieve your IAM role's credentials and access the SNS topic, so you don't have to add any user ceredentials.
-
-In OpenSearch Dashboards, choose **Create**.
-
-#### Adding access key and secret access key
-
-After ensuring that your IAM user has the necessary trust relationship and permissions, run the following commands in your terminal and follow the prompts to add your IAM user's access key and secret key.
-
-```
-./bin/opensearch-keystore add opensearch.alerting.destination.sns.access.key
-./bin/opensearch-keystore add opensearch.alerting.destination.sns.secret.key
-```
-
-In OpenSearch Dashboards, choose **Create**.
 
 ### Email as a destination
 
@@ -132,8 +78,8 @@ You can enter individual email addresses or an email group in the **Recipients**
 If your email provider requires SSL or TLS, you must authenticate each sender account before you can send an email. Enter these credentials in the OpenSearch keystore using the CLI. Run the following commands (in your OpenSearch directory) to enter your username and password. The `<sender_name>` is the name you entered for **Sender** earlier.
 
 ```bash
-./bin/opensearch-keystore add opensearch.alerting.destination.email.<sender_name>.username
-./bin/opensearch-keystore add opensearch.alerting.destination.email.<sender_name>.password
+./bin/opensearch-keystore add plugins.alerting.destination.email.<sender_name>.username
+./bin/opensearch-keystore add plugins.alerting.destination.email.<sender_name>.password
 ```
 
 **Note**: Keystore settings are node-specific. You must run these commands on each node.
@@ -148,6 +94,7 @@ POST _nodes/reload_secure_settings
 }
 ```
 
+
 ---
 
 ## Create monitors
@@ -155,7 +102,7 @@ POST _nodes/reload_secure_settings
 1. Choose **Alerting**, **Monitors**, **Create monitor**.
 1. Specify a name for the monitor.
 
-The anomaly detection option is for pairing with the anomaly detection plugin. See [Anomaly Detection](../../ad/).
+The anomaly detection option is for pairing with the anomaly detection plugin. See [Anomaly Detection]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/).
 For anomaly detector, choose an appropriate schedule for the monitor based on the detector interval. Otherwise, the alerting monitor might miss reading the results.
 
 For example, assume you set the monitor interval and the detector interval as 5 minutes, and you start the detector at 12:00. If an anomaly is detected at 12:05, it might be available at 12:06 because of the delay between writing the anomaly and it being available for queries. The monitor reads the anomaly results between 12:00 and 12:05, so it does not get the anomaly results available at 12:06.
@@ -167,13 +114,13 @@ Whenever you update a detector’s interval, make sure to update the associated
 
 1. Choose one or more indices. You can also use `*` as a wildcard to specify an index pattern.
 
-   If you use the security plugin, you can only choose indices that you have permission to access. For details, see [Alerting security](../security/).
+   If you use the security plugin, you can only choose indices that you have permission to access. For details, see [Alerting security]({{site.url}}{{site.baseurl}}/security-plugin/).
 
 1. Define the monitor in one of three ways: visually, using a query, or using an anomaly detector.
 
    - Visual definition works well for monitors that you can define as "some value is above or below some threshold for some amount of time."
 
-   - Query definition gives you flexibility in terms of what you query for (using [the OpenSearch query DSL](../../opensearch/full-text)) and how you evaluate the results of that query (Painless scripting).
+   - Query definition gives you flexibility in terms of what you query for (using [the OpenSearch query DSL]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text)) and how you evaluate the results of that query (Painless scripting).
 
      This example averages the `cpu_usage` field:
 
@@ -225,12 +172,12 @@ Whenever you update a detector’s interval, make sure to update the associated
 
 1. To define a monitor visually, choose **Define using visual graph**. Then choose an aggregation (for example, `count()` or `average()`), a set of documents, and a timeframe. Visual definition works well for most monitors.
 
-   To use a query, choose **Define using extraction query**, add your query (using [the OpenSearch query DSL](../../opensearch/full-text/)), and test it using the **Run** button.
+   To use a query, choose **Define using extraction query**, add your query (using [the OpenSearch query DSL]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/)), and test it using the **Run** button.
 
    The monitor makes this query to OpenSearch as often as the schedule dictates; check the **Query Performance** section and make sure you're comfortable with the performance implications.
 
    To use an anomaly detector, choose **Define using Anomaly detector** and select your **Detector**.
-1. Choose a frequency and timezone for your monitor. Note that you can only pick a timezone if you choose Daily, Weekly, Monthly, or [custom cron expression](../cron/) for frequency.
+1. Choose a frequency and timezone for your monitor. Note that you can only pick a timezone if you choose Daily, Weekly, Monthly, or [custom cron expression]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/cron/) for frequency.
 1. Choose **Create**.
 
 
@@ -318,7 +265,7 @@ Below are some variables you can include in your message using Mustache template
 Variable | Data Type | Description
 :--- | :--- | :---
 `ctx.monitor` | JSON | Includes `ctx.monitor.name`, `ctx.monitor.type`, `ctx.monitor.enabled`, `ctx.monitor.enabled_time`, `ctx.monitor.schedule`, `ctx.monitor.inputs`, `triggers` and `ctx.monitor.last_update_time`.
-`ctx.monitor.user` | JSON | Includes information about the user who created the monitor. Includes `ctx.monitor.user.backend_roles` and `ctx.monitor.user.roles`, which are arrays that contain the backend roles and roles assigned to the user. See [alerting security](../security/) for more information.
+`ctx.monitor.user` | JSON | Includes information about the user who created the monitor. Includes `ctx.monitor.user.backend_roles` and `ctx.monitor.user.roles`, which are arrays that contain the backend roles and roles assigned to the user. See [alerting security]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/security/) for more information.
 `ctx.monitor.enabled` | Boolean | Whether the monitor is enabled.
 `ctx.monitor.enabled_time` | Milliseconds | Unix epoch time of when the monitor was last enabled.
 `ctx.monitor.schedule` | JSON | Contains a schedule of how often or when the monitor should run.
@@ -369,7 +316,7 @@ Variable | Data Type | Description
 
 ## Add actions
 
-The final step in creating a monitor is to add one or more actions. Actions send notifications when trigger conditions are met and support [Slack](https://slack.com/), [Amazon Chime](https://aws.amazon.com/chime/), [Amazon Simple Notification Service](https://aws.amazon.com/sns/), and webhooks.
+The final step in creating a monitor is to add one or more actions. Actions send notifications when trigger conditions are met and support [Slack](https://slack.com/), [Amazon Chime](https://aws.amazon.com/chime/), and webhooks.
 
 If you don't want to receive notifications for alerts, you don't have to add actions to your triggers. Instead, you can periodically check OpenSearch Dashboards.
 {: .tip }

_monitoring-plugins/alerting/security.md

@@ -1,6 +1,6 @@
 ---
 layout: default
-title: Alerting Security
+title: Alerting security
 nav_order: 10
 parent: Alerting
 has_children: false
@@ -13,9 +13,9 @@ If you use the security plugin alongside alerting, you might want to limit certa
 
 ## Basic permissions
 
-The security plugin has three built-in roles that cover most alerting use cases: `alerting_read_access`, `alerting_ack_alerts`, and `alerting_full_access`. For descriptions of each, see [Predefined roles](../../security/access-control/users-roles/#predefined-roles).
+The security plugin has three built-in roles that cover most alerting use cases: `alerting_read_access`, `alerting_ack_alerts`, and `alerting_full_access`. For descriptions of each, see [Predefined roles]({{site.url}}{{site.baseurl}}/security-plugin/access-control/users-roles#predefined-roles).
 
-If these roles don't meet your needs, mix and match individual alerting [permissions](../../security/access-control/permissions/) to suit your use case. Each action corresponds to an operation in the REST API. For example, the `cluster:admin/opensearch/alerting/destination/delete` permission lets you delete destinations.
+If these roles don't meet your needs, mix and match individual alerting [permissions]({{site.url}}{{site.baseurl}}/security-plugin/access-control/permissions/) to suit your use case. Each action corresponds to an operation in the REST API. For example, the `cluster:admin/opensearch/alerting/destination/delete` permission lets you delete destinations.
 
 
 ## How monitors access data
@@ -29,14 +29,14 @@ Later, the user `psantos` wants to edit the monitor to run every two hours, but
 - Update the monitor so that it only checks `store1-returns`.
 - Ask an administrator for read access to the other two indices.
 
-After making the change, the monitor now runs with the same permissions as `psantos`, including any [document-level security](../../security/access-control/document-level-security/) queries, [excluded fields](../../security/access-control/field-level-security/), and [masked fields](../../security/access-control/field-masking/). If you use an extraction query to define your monitor, use the **Run** button to ensure that the response includes the fields you need.
+After making the change, the monitor now runs with the same permissions as `psantos`, including any [document-level security]({{site.url}}{{site.baseurl}}/security-plugin/access-control/document-level-security/) queries, [excluded fields]({{site.url}}{{site.baseurl}}/security-plugin/access-control/field-level-security/), and [masked fields]({{site.url}}{{site.baseurl}}/security-plugin/access-control/field-masking/). If you use an extraction query to define your monitor, use the **Run** button to ensure that the response includes the fields you need.
 
 
 ## (Advanced) Limit access by backend role
 
 Out of the box, the alerting plugin has no concept of ownership. For example, if you have the `cluster:admin/opensearch/alerting/monitor/write` permission, you can edit *all* monitors, regardless of whether you created them. If a small number of trusted users manage your monitors and destinations, this lack of ownership generally isn't a problem. A larger organization might need to segment access by backend role.
 
-First, make sure that your users have the appropriate [backend roles](../../security/access-control/). Backend roles usually come from an [LDAP server](../../security/configuration/ldap/) or [SAML provider](../../security/configuration/saml/). However, if you use the internal user database, you can use the REST API to [add them manually](../../security/access-control/api/#create-user).
+First, make sure that your users have the appropriate [backend roles]({{site.url}}{{site.baseurl}}/security-plugin/access-control/index/). Backend roles usually come from an [LDAP server]({{site.url}}{{site.baseurl}}/security-plugin/configuration/ldap/) or [SAML provider]({{site.url}}{{site.baseurl}}/security-plugin/configuration/saml/). However, if you use the internal user database, you can use the REST API to [add them manually]({{site.url}}{{site.baseurl}}/security-plugin/access-control/api#create-user).
 
 Next, enable the following setting:
 
@@ -44,7 +44,7 @@ Next, enable the following setting:
 PUT _cluster/settings
 {
   "transient": {
-    "opendistro.alerting.filter_by_backend_roles": "true"
+    "plugins.alerting.filter_by_backend_roles": "true"
   }
 }
 ```
@@ -58,7 +58,7 @@ If `jdoe` creates a monitor, `jroe` can see and modify it, but `psantos` can't.
 
 <!-- ## (Advanced) Limit access by individual
 
-If you only want users to be able to see and modify their own monitors and destinations, duplicate the `alerting_full_access` role and add the following [DLS query](../../security/access-control/document-level-security/) to it:
+If you only want users to be able to see and modify their own monitors and destinations, duplicate the `alerting_full_access` role and add the following [DLS query]({{site.url}}{{site.baseurl}}/security-plugin/access-control/document-level-security/) to it:
 
 ```json
 {

_monitoring-plugins/alerting/settings.md

@@ -0,0 +1,59 @@
+---
+layout: default
+title: Management
+parent: Alerting
+nav_order: 5
+---
+
+# Management
+
+
+## Alerting indices
+
+The alerting feature creates several indices and one alias. The security plugin demo script configures them as [system indices]({{site.url}}{{site.baseurl}}/security-plugin/configuration/system-indices/) for an extra layer of protection. Don't delete these indices or modify their contents without using the alerting APIs.
+
+Index | Purpose
+:--- | :---
+`.opendistro-alerting-alerts` | Stores ongoing alerts.
+`.opendistro-alerting-alert-history-<date>` | Stores a history of completed alerts.
+`.opendistro-alerting-config` | Stores monitors, triggers, and destinations. [Take a snapshot]({{site.url}}{{site.baseurl}}/opensearch/snapshot-restore) of this index to back up your alerting configuration.
+`.opendistro-alerting-alert-history-write` (alias) | Provides a consistent URI for the `.opendistro-alerting-alert-history-<date>` index.
+
+All alerting indices are hidden by default. For a summary, make the following request:
+
+```
+GET _cat/indices?expand_wildcards=open,hidden
+```
+
+
+## Alerting settings
+
+We don't recommend changing these settings; the defaults should work well for most use cases.
+
+All settings are available using the OpenSearch `_cluster/settings` API. None require a restart, and all can be marked `persistent` or `transient`.
+
+Setting | Default | Description
+:--- | :--- | :---
+`plugins.scheduled_jobs.enabled` | true | Whether the alerting plugin is enabled or not. If disabled, all monitors immediately stop running.
+`plugins.alerting.index_timeout` | 60s | The timeout for creating monitors and destinations using the REST APIs.
+`plugins.alerting.request_timeout` | 10s | The timeout for miscellaneous requests from the plugin.
+`plugins.alerting.action_throttle_max_value` | 24h | The maximum amount of time you can set for action throttling. By default, this value displays as 1440 minutes in OpenSearch Dashboards.
+`plugins.alerting.input_timeout` | 30s | How long the monitor can take to issue the search request.
+`plugins.alerting.bulk_timeout` | 120s | How long the monitor can write alerts to the alert index.
+`plugins.alerting.alert_backoff_count` | 3 | The number of retries for writing alerts before the operation fails.
+`plugins.alerting.alert_backoff_millis` | 50ms | The amount of time to wait between retries---increases exponentially after each failed retry.
+`plugins.alerting.alert_history_rollover_period` | 12h | How frequently to check whether the `.opendistro-alerting-alert-history-write` alias should roll over to a new history index and whether the Alerting plugin should delete any history indices.
+`plugins.alerting.move_alerts_backoff_millis` | 250 | The amount of time to wait between retries---increases exponentially after each failed retry.
+`plugins.alerting.move_alerts_backoff_count` | 3 | The number of retries for moving alerts to a deleted state after their monitor or trigger has been deleted.
+`plugins.alerting.monitor.max_monitors` | 1000 | The maximum number of monitors users can create.
+`plugins.alerting.alert_history_max_age` | 30d | The oldest document to store in the `.opendistro-alert-history-<date>` index before creating a new index. If the number of alerts in this time period does not exceed `alert_history_max_docs`, alerting creates one history index per period (e.g. one index every 30 days).
+`plugins.alerting.alert_history_max_docs` | 1000 | The maximum number of alerts to store in the `.opendistro-alert-history-<date>` index before creating a new index.
+`plugins.alerting.alert_history_enabled` | true | Whether to create `.opendistro-alerting-alert-history-<date>` indices.
+`plugins.alerting.alert_history_retention_period` | 60d | The amount of time to keep history indices before automatically deleting them.
+`plugins.alerting.destination.allow_list` | ["chime", "slack", "custom_webhook", "email", "test_action"] | The list of allowed destinations. If you don't want to allow users to a certain type of destination, you can remove it from this list, but we recommend leaving this setting as-is.
+`plugins.alerting.filter_by_backend_roles` | "false" | Restricts access to monitors by backend role. See [Alerting security]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/security/).
+`plugins.scheduled_jobs.sweeper.period` | 5m | The alerting feature uses its "job sweeper" component to periodically check for new or updated jobs. This setting is the rate at which the sweeper checks to see if any jobs (monitors) have changed and need to be rescheduled.
+`plugins.scheduled_jobs.sweeper.page_size` | 100 | The page size for the sweeper. You shouldn't need to change this value.
+`plugins.scheduled_jobs.sweeper.backoff_millis` | 50ms | The amount of time the sweeper waits between retries---increases exponentially after each failed retry.
+`plugins.scheduled_jobs.sweeper.retry_count` | 3 | The total number of times the sweeper should retry before throwing an error.
+`plugins.scheduled_jobs.request_timeout` | 10s | The timeout for the request that sweeps shards for jobs.

_monitoring-plugins/pa/api.md

@@ -10,7 +10,7 @@ nav_order: 1
 Performance Analyzer uses a single HTTP method and URI for most requests:
 
 ```
-GET <endpoint>:9600/_opensearch/_performanceanalyzer/metrics
+GET <endpoint>:9600/_plugins/_performanceanalyzer/metrics
 ```
 
 Note the use of port 9600. Provide parameters for metrics, aggregations, dimensions, and nodes (optional):
@@ -19,13 +19,13 @@ Note the use of port 9600. Provide parameters for metrics, aggregations, dimensi
 ?metrics=<metrics>&agg=<aggregations>&dim=<dimensions>&nodes=all"
 ```
 
-For a full list of metrics, see [Metrics reference](../reference/). Performance Analyzer updates its data every five seconds. If you create a custom client, we recommend using that same interval for calls to the API.
+For a full list of metrics, see [Metrics reference]({{site.url}}{{site.baseurl}}/monitoring-plugins/pa/reference/). Performance Analyzer updates its data every five seconds. If you create a custom client, we recommend using that same interval for calls to the API.
 
 
 #### Sample request
 
 ```
-GET localhost:9600/_opensearch/_performanceanalyzer/metrics?metrics=Latency,CPU_Utilization&agg=avg,max&dim=ShardID&nodes=all
+GET localhost:9600/_plugins/_performanceanalyzer/metrics?metrics=Latency,CPU_Utilization&agg=avg,max&dim=ShardID&nodes=all
 ```
 
 
@@ -104,7 +104,7 @@ Performance Analyzer has one additional URI that returns the unit for each metri
 #### Sample request
 
 ```
-GET localhost:9600/_opensearch/_performanceanalyzer/metrics/units
+GET localhost:9600/_plugins/_performanceanalyzer/metrics/units
 ```
 
 

_monitoring-plugins/pa/dashboards.md

@@ -32,7 +32,7 @@ The best way to get started with building custom dashboards is to duplicate and
 
 PerfTop positions elements within a grid. For example, consider this 12 * 12 grid.
 
-![Dashboard grid](../../images/perftop-grid.png)
+![Dashboard grid]({{site.url}}{{site.baseurl}}/images/perftop-grid.png)
 
 The upper-left of the grid represents row 0, column 0, so the starting positions for the three boxes are:
 
@@ -95,7 +95,7 @@ At this point, however, all the JSON does is define the size and position of thr
 
 ## Add queries
 
-Queries use the same elements as the [REST API](../api/), just in JSON form:
+Queries use the same elements as the [REST API]({{site.url}}{{site.baseurl}}/monitoring-plugins/pa/api/), just in JSON form:
 
 ```json
 {
@@ -108,7 +108,7 @@ Queries use the same elements as the [REST API](../api/), just in JSON form:
 }
 ```
 
-For details on available metrics, see [Metrics reference](../reference/).
+For details on available metrics, see [Metrics reference]({{site.url}}{{site.baseurl}}/monitoring-plugins/pa/reference/).
 
 
 ## Add options

_monitoring-plugins/pa/index.md

@@ -3,6 +3,8 @@ layout: default
 title: Performance Analyzer
 nav_order: 58
 has_children: true
+redirect_from:
+  - /monitoring-plugins/pa/
 ---
 
 # Performance Analyzer
@@ -17,7 +19,7 @@ You can also install it using [npm](https://www.npmjs.com/):
 npm install -g @aws/opensearch-perftop
 ```
 
-![PerfTop screenshot](../images/perftop.png)
+![PerfTop screenshot]({{site.url}}{{site.baseurl}}/images/perftop.png)
 
 
 ## Get started with PerfTop
@@ -25,28 +27,28 @@ npm install -g @aws/opensearch-perftop
 The basic syntax is:
 
 ```bash
-./perf-top-<operating_system> --dashboard <dashboard>.json --endpoint <endpoint>
+./opensearch-perf-top-<operating_system> --dashboard <dashboard>.json --endpoint <endpoint>
 ```
 
 If you're using npm, the syntax is similar:
 
 ```bash
-perf-top --dashboard <dashboard> --endpoint <endpoint>
+opensearch-perf-top --dashboard <dashboard> --endpoint <endpoint>
 ```
 
 If you're running PerfTop from a node (i.e. locally), specify port 9600:
 
 ```bash
-./perf-top-linux --dashboard dashboards/<dashboard>.json --endpoint localhost:9600
+./opensearch-perf-top-linux --dashboard dashboards/<dashboard>.json --endpoint localhost:9600
 ```
 
 Otherwise, just specify the OpenSearch endpoint:
 
 ```bash
-./perf-top-macos --dashboard dashboards/<dashboard>.json --endpoint my-cluster.my-domain.com
+./opensearch-perf-top-macos --dashboard dashboards/<dashboard>.json --endpoint my-cluster.my-domain.com
 ```
 
-PerfTop has four pre-built dashboards in the `dashboards` directory, but you can also [create your own](dashboards/).
+PerfTop has four pre-built dashboards in the `dashboards` directory, but you can also [create your own]({{site.url}}{{site.baseurl}}/dashboards/).
 
 You can also load the pre-built dashboards (ClusterOverview, ClusterNetworkMemoryAnalysis, ClusterThreadAnalysis, or NodeAnalysis) without the JSON files, such as `--dashboard ClusterThreadAnalysis`.
 
@@ -66,7 +68,7 @@ PerfTop has no interactivity. Start the application, monitor the dashboard, and
 
 Performance Analyzer uses `/dev/shm` for temporary storage. During heavy workloads on a cluster, Performance Analyzer can use up to 1 GB of space.
 
-Docker, however, has a default `/dev/shm` size of 64 MB. To change this value, you can use the `docker run --shm-size 1gb` flag or [a similar setting in Docker Compose](https://docs.docker.com/compose/compose-file/#shm_size).
+Docker, however, has a default `/dev/shm` size of 64 MB. To change this value, you can use the `docker run --shm-size 1gb` flag or [a similar setting in Docker Compose](https://docs.docker.com/compose/compose-file#shm_size).
 
 If you're not using Docker, check the size of `/dev/shm` using `df -h`. The default value is probably plenty, but if you need to change its size, add the following line to `/etc/fstab`:
 
@@ -83,10 +85,10 @@ mount -o remount /dev/shm
 
 ### Security
 
-Performance Analyzer supports encryption in transit for requests. It currently does *not* support client or server authentication for requests. To enable encryption in transit, edit `performance-analyzer.properties` in your `$ES_HOME` directory:
+Performance Analyzer supports encryption in transit for requests. It currently does *not* support client or server authentication for requests. To enable encryption in transit, edit `performance-analyzer.properties` in your `$OPENSEARCH_HOME` directory:
 
 ```bash
-vi $ES_HOME/plugins/opensearch_performance_analyzer/pa_config/performance-analyzer.properties
+vi $OPENSEARCH_HOME/plugins/opensearch-performance-analyzer/pa_config/performance-analyzer.properties
 ```
 
 Change the following lines to configure encryption in transit. Note that `certificate-file-path` must be a certificate for the server, not a root CA:

_monitoring-plugins/pa/rca/api.md

@@ -12,10 +12,10 @@ nav_order: 1
 
 ```
 # Request all available RCAs
-GET localhost:9600/_opensearch/_performanceanalyzer/rca
+GET localhost:9600/_plugins/_performanceanalyzer/rca
 
 # Request a specific RCA
-GET localhost:9600/_opensearch/_performanceanalyzer/rca?name=HighHeapUsageClusterRca
+GET localhost:9600/_plugins/_performanceanalyzer/rca?name=HighHeapUsageClusterRca
 ```
 
 

_monitoring-plugins/pa/rca/reference.md

@@ -8,4 +8,4 @@ nav_order: 3
 
 # RCA reference
 
-You can find a reference of available RCAs and their purposes on [Github](https://github.com/opensearch-project/performance-analyzer-rca/tree/master/docs).
+You can find a reference of available RCAs and their purposes on [GitHub](https://github.com/opensearch-project/performance-analyzer-rca/tree/main/docs).

_monitoring-plugins/trace/data-prepper-reference.md

@@ -7,7 +7,7 @@ nav_order: 25
 
 # Data Prepper configuration reference
 
-This page lists all supported Data Prepper sources, buffers, preppers, and sinks, along with their associated options. For example configuration files, see [Data Prepper](../data-prepper/).
+This page lists all supported Data Prepper sources, buffers, preppers, and sinks, along with their associated options. For example configuration files, see [Data Prepper]({{site.url}}{{site.baseurl}}/monitoring-plugins/trace/data-prepper/).
 
 
 ## Data Prepper server options
@@ -149,7 +149,7 @@ aws_region | No | String, AWS region for the cluster (e.g. `"us-east-1"`) if you
 trace_analytics_raw | No | Boolean, default false. Whether to export as trace data to the `otel-v1-apm-span-*` index pattern (alias `otel-v1-apm-span`) for use with the Trace Analytics OpenSearch Dashboards plugin.
 trace_analytics_service_map | No | Boolean, default false. Whether to export as trace data to the `otel-v1-apm-service-map` index for use with the service map component of the Trace Analytics OpenSearch Dashboards plugin.
 index | No | String, name of the index to export to. Only required if you don't use the `trace_analytics_raw` or `trace_analytics_service_map` presets.
-template_file | No | String, the path to a JSON [index template](../../opensearch/index-templates/) file (e.g. `/your/local/template-file.json` if you do not use the `trace_analytics_raw` or `trace_analytics_service_map`. See [otel-v1-apm-span-index-template.json](https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/opensearch/src/main/resources/otel-v1-apm-span-index-template.json) for an example.
+template_file | No | String, the path to a JSON [index template]({{site.url}}{{site.baseurl}}/opensearch/index-templates/) file (e.g. `/your/local/template-file.json` if you do not use the `trace_analytics_raw` or `trace_analytics_service_map`. See [otel-v1-apm-span-index-template.json](https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/opensearch/src/main/resources/otel-v1-apm-span-index-template.json) for an example.
 document_id_field | No | String, the field from the source data to use for the OpenSearch document ID (e.g. `"my-field"`) if you don't use the `trace_analytics_raw` or `trace_analytics_service_map` presets.
 dlq_file | No | String, the path to your preferred dead letter queue file (e.g. `/your/local/dlq-file`). Data Prepper writes to this file when it fails to index a document on the OpenSearch cluster.
 bulk_size | No | Integer (long), default 5. The maximum size (in MiB) of bulk requests to the OpenSearch cluster. Values below 0 indicate an unlimited size. If a single document exceeds the maximum bulk request size, Data Prepper sends it individually.

_monitoring-plugins/trace/data-prepper.md

@@ -15,7 +15,7 @@ Data Prepper is an independent component, not an OpenSearch plugin, that convert
 To use the Docker image, pull it like any other image:
 
 ```bash
-docker pull opensearch/opensearch-data-prepper:latest
+docker pull opensearchproject/data-prepper:latest
 ```
 
 Otherwise, [download](https://opensearch.org/downloads.html) the appropriate archive for your operating system and unzip it.
@@ -105,7 +105,7 @@ service-map-pipeline:
         trace_analytics_service_map: true
 ```
 
-To learn more, see the [Data Prepper configuration reference](../data-prepper-reference/).
+To learn more, see the [Data Prepper configuration reference]({{site.url}}{{site.baseurl}}/monitoring-plugins/trace/data-prepper-reference/).
 
 ## Configure the Data Prepper server
 Data Prepper itself provides administrative HTTP endpoints such as `/list` to list pipelines and `/metrics/prometheus` to provide Prometheus-compatible metrics data. The port which serves these endpoints, as well as TLS configuration, is specified by a separate YAML file. Example:

_monitoring-plugins/trace/get-started.md

@@ -12,7 +12,7 @@ OpenSearch Trace Analytics consists of two components---Data Prepper and the Tra
 
 ## Basic flow of data
 
-![Data flow diagram from a distributed application to OpenSearch](../../images/ta.svg)
+![Data flow diagram from a distributed application to OpenSearch]({{site.url}}{{site.baseurl}}/images/ta.svg)
 
 1. Trace Analytics relies on you adding instrumentation to your application and generating trace data. The [OpenTelemetry documentation](https://opentelemetry.io/docs/) contains example applications for many programming languages that can help you get started, including Java, Python, Go, and JavaScript.
 
@@ -20,9 +20,9 @@ OpenSearch Trace Analytics consists of two components---Data Prepper and the Tra
 
 1. The [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/) receives data from the application and formats it into OpenTelemetry data.
 
-1. [Data Prepper](../data-prepper/) processes the OpenTelemetry data, transforms it for use in OpenSearch, and indexes it on an OpenSearch cluster.
+1. [Data Prepper]({{site.url}}{{site.baseurl}}/monitoring-plugins/trace/data-prepper/) processes the OpenTelemetry data, transforms it for use in OpenSearch, and indexes it on an OpenSearch cluster.
 
-1. The [Trace Analytics OpenSearch Dashboards plugin](../ta-opensearch-dashboards/) displays the data in near real-time as a series of charts and tables, with an emphasis on service architecture, latency, error rate, and throughput.
+1. The [Trace Analytics OpenSearch Dashboards plugin]({{site.url}}{{site.baseurl}}/monitoring-plugins/trace/ta-dashboards/) displays the data in near real-time as a series of charts and tables, with an emphasis on service architecture, latency, error rate, and throughput.
 
 
 ## Jaeger HotROD
@@ -39,7 +39,7 @@ Download or clone the [Data Prepper repository](https://github.com/opensearch-pr
 
 Close the file and run `docker-compose up --build`. After the containers start, navigate to `http://localhost:8080` in a web browser.
 
-![HotROD web interface](../../images/hot-rod.png)
+![HotROD web interface]({{site.url}}{{site.baseurl}}/images/hot-rod.png)
 
 Click one of the buttons in the web interface to send a request to the application. Each request starts a series of operations across the services that make up the application. From the console logs, you can see that these operations share the same `trace-id`, which lets you track all of the operations in the request as a single *trace*:
 
@@ -80,4 +80,4 @@ curl -X GET -u 'admin:admin' -k 'https://localhost:9200/otel-v1-apm-span-000001/
 
 Navigate to `http://localhost:5601` in a web browser and choose **Trace Analytics**. You can see the results of your single click in the Jaeger HotROD web interface: the number of traces per API and HTTP method, latency trends, a color-coded map of the service architecture, and a list of trace IDs that you can use to drill down on individual operations.
 
-If you don't see your trace, adjust the timeframe in OpenSearch Dashboards. For more information on using the plugin, see [OpenSearch Dashboards plugin](../ta-opensearch-dashboards/).
+If you don't see your trace, adjust the timeframe in OpenSearch Dashboards. For more information on using the plugin, see [OpenSearch Dashboards plugin]({{site.url}}{{site.baseurl}}/monitoring-plugins/trace/ta-dashboards/).

_monitoring-plugins/trace/index.md

@@ -4,6 +4,8 @@ title: Trace analytics
 nav_order: 48
 has_children: true
 has_toc: false
+redirect_from:
+  - /monitoring-plugins/trace/
 ---
 
 # Trace Analytics
@@ -14,4 +16,4 @@ A single operation, such as a user clicking a button, can trigger an extended se
 
 Trace Analytics can help you visualize this flow of events and identify performance problems.
 
-![Detailed trace view](../images/ta-trace.png)
+![Detailed trace view]({{site.url}}{{site.baseurl}}/images/ta-trace.png)

_monitoring-plugins/trace/ta-dashboards.md

@@ -7,16 +7,16 @@ nav_order: 50
 
 # Trace Analytics OpenSearch Dashboards plugin
 
-The Trace Analytics plugin for OpenSearch Dashboards provides at-a-glance visibility into your application performance, along with the ability to drill down on individual traces. For installation instructions, see [Standalone OpenSearch Dashboards plugin install](../../opensearch-dashboards/plugins/).
+The Trace Analytics plugin for OpenSearch Dashboards provides at-a-glance visibility into your application performance, along with the ability to drill down on individual traces. For installation instructions, see [Standalone OpenSearch Dashboards plugin install]({{site.url}}{{site.baseurl}}/dashboards/install/plugins/).
 
 The **Dashboard** view groups traces together by HTTP method and path so that you can see the average latency, error rate, and trends associated with a particular operation. For a more focused view, try filtering by trace group name.
 
-![Dashboard view](../../images/ta-dashboard.png)
+![Dashboard view]({{site.url}}{{site.baseurl}}/images/ta-dashboard.png)
 
 To drill down on the traces that make up a trace group, choose the number of traces in righthand column. Then choose an individual trace for a detailed summary.
 
-![Detailed trace view](../../images/ta-trace.png)
+![Detailed trace view]({{site.url}}{{site.baseurl}}/images/ta-trace.png)
 
 The **Services** view lists all services in the application, plus an interactive map that shows how the various services connect to each other. In contrast to the dashboard, which helps identify problems by operation, the service map helps identify problems by service. Try sorting by error rate or latency to get a sense of potential problem areas of your application.
 
-![Service view](../../images/ta-services.png)
+![Service view]({{site.url}}{{site.baseurl}}/images/ta-services.png)

_opensearch/aggregations.md

@@ -1,8 +1,7 @@
 ---
 layout: default
 title: Aggregations
-parent: OpenSearch
-nav_order: 13
+nav_order: 14
 has_children: true
 ---
 
@@ -16,13 +15,13 @@ OpenSearch can perform aggregations on massive datasets in milliseconds. Compare
 
 ## Aggregations on text fields
 
-By default, OpenSearch doesn't support aggregations on a text field.
-Because text fields are tokenized, an aggregation on a text field has to reverse the tokenization process back to its original string and then formulate an aggregation based on that. Such an operation consumes significant memory and degrades cluster performance.
+By default, OpenSearch doesn't support aggregations on a text field. Because text fields are tokenized, an aggregation on a text field has to reverse the tokenization process back to its original string and then formulate an aggregation based on that. This kind of an operation consumes significant memory and degrades cluster performance.
 
 While you can enable aggregations on text fields by setting the `fielddata` parameter to `true` in the mapping, the aggregations are still based on the tokenized words and not on the raw text.
 
 We recommend keeping a raw version of the text field as a `keyword` field that you can aggregate on.
-In this case, you can perform aggregations on the `title.raw` field, instead of the `title` field:
+
+In this case, you can perform aggregations on the `title.raw` field, instead of on the `title` field:
 
 ```json
 PUT movies
@@ -61,15 +60,13 @@ GET _search
 
 If you’re only interested in the aggregation result and not in the results of the query, set `size` to 0.
 
-In the `aggs` property (you can use `aggregations` if you want), you can define any number of aggregations.
-Each aggregation is defined by its name and one of the types of aggregations that OpenSearch supports.
+In the `aggs` property (you can use `aggregations` if you want), you can define any number of aggregations. Each aggregation is defined by its name and one of the types of aggregations that OpenSearch supports.
 
-The name of the aggregation helps you to distinguish between different aggregations in the response.
-The `AGG_TYPE` property is where you specify the type of aggregation.
+The name of the aggregation helps you to distinguish between different aggregations in the response. The `AGG_TYPE` property is where you specify the type of aggregation.
 
 ## Sample aggregation
 
-This section uses the OpenSearch Dashboards sample e-commerce data and web log data. To add the sample data, log in to OpenSearch Dashboards, choose **Home** and **Try our sample data**. For **Sample eCommerce orders** and **Sample web logs**, choose **Add data**.
+This section uses the OpenSearch Dashboards sample ecommerce data and web log data. To add the sample data, log in to OpenSearch Dashboards, choose **Home**, and then choose **Try our sample data**. For **Sample eCommerce orders** and **Sample web logs**, choose **Add data**.
 
 ### avg
 
@@ -129,7 +126,7 @@ There are three main types of aggregations:
 
 ## Nested aggregations
 
-Aggregations within aggregations are called nested or sub aggregations.
+Aggregations within aggregations are called nested or subaggregations.
 
 Metric aggregations produce simple results and can't contain nested aggregations.
 

_opensearch/bucket-agg.md

@@ -2,16 +2,15 @@
 layout: default
 title: Bucket Aggregations
 parent: Aggregations
-grand_parent: OpenSearch
 nav_order: 2
 has_children: false
 ---
 
-# Bucket Aggregations
+# Bucket aggregations
 
 Bucket aggregations categorize sets of documents as buckets. The type of bucket aggregation determines whether a given document falls into a bucket or not.
 
-You can use bucket aggregations to implement faceted navigation (usually placed as a sidebar on a search result landing page) to help you're users narrow down the results.
+You can use bucket aggregations to implement faceted navigation (usually placed as a sidebar on a search result landing page) to help your users narrow down the results.
 
 ## terms
 

_opensearch/cluster.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Cluster formation
-parent: OpenSearch
 nav_order: 7
 ---
 
@@ -15,7 +14,7 @@ To create and deploy an OpenSearch cluster according to your requirements, it’
 
 There are many ways to design a cluster. The following illustration shows a basic architecture:
 
-![multi-node cluster architecture diagram](../../images/cluster.png)
+![multi-node cluster architecture diagram]({{site.url}}{{site.baseurl}}/images/cluster.png)
 
 This is a four-node cluster that has one dedicated master node, one dedicated coordinating node, and two data nodes that are master-eligible and also used for ingesting data.
 
@@ -37,7 +36,7 @@ This page demonstrates how to work with the different node types. It assumes tha
 
 ## Prerequisites
 
-Before you get started, you must install and configure OpenSearch on all of your nodes. For information about the available options, see [Install and configure OpenSearch](../../install/).
+Before you get started, you must install and configure OpenSearch on all of your nodes. For information about the available options, see [Install and configure OpenSearch]({{site.url}}{{site.baseurl}}/opensearch/install/).
 
 After you're done, use SSH to connect to each node, then open the `config/opensearch.yml` file. You can set all configurations for your cluster in this file.
 
@@ -189,7 +188,7 @@ x.x.x.x           34          38   0    0.12    0.07     0.06 md        -      o
 x.x.x.x           23          38   0    0.12    0.07     0.06 md        -      opensearch-c1
 ```
 
-To better understand and monitor your cluster, use the [cat API](../catapis/).
+To better understand and monitor your cluster, use the [cat API]({{site.url}}{{site.baseurl}}/opensearch/catapis/).
 
 
 ## (Advanced) Step 6: Configure shard allocation awareness or forced awareness
@@ -323,9 +322,9 @@ old_index 0     r      UNASSIGNED
 
 In this case, all primary shards are allocated to `opensearch-d2`. Again, all replica shards are unassigned because we only have one warm node.
 
-A popular approach is to configure your [index templates](../index-templates/) to set the `index.routing.allocation.require.temp` value to `hot`. This way, OpenSearch stores your most recent data on your hot nodes.
+A popular approach is to configure your [index templates]({{site.url}}{{site.baseurl}}/opensearch/index-templates/) to set the `index.routing.allocation.require.temp` value to `hot`. This way, OpenSearch stores your most recent data on your hot nodes.
 
-You can then use the [Index State Management (ISM)](../../ism/index/) plugin to periodically check the age of an index and specify actions to take on it. For example, when the index reaches a specific age, change the `index.routing.allocation.require.temp` setting to `warm` to automatically move your data from hot nodes to warm nodes.
+You can then use the [Index State Management (ISM)]({{site.url}}{{site.baseurl}}/im-plugin/) plugin to periodically check the age of an index and specify actions to take on it. For example, when the index reaches a specific age, change the `index.routing.allocation.require.temp` setting to `warm` to automatically move your data from hot nodes to warm nodes.
 
 
 ## Next steps
@@ -333,7 +332,7 @@ You can then use the [Index State Management (ISM)](../../ism/index/) plugin to
 If you are using the security plugin, the previous request to `_cat/nodes?v` might have failed with an initialization error. To initialize the plugin, run `opensearch/plugins/opensearch-security/tools/securityadmin.sh`. A sample command that uses the demo certificates might look like this:
 
 ```bash
-sudo ./securityadmin.sh -cd ../securityconfig/ -icl -nhnv -cacert /etc/opensearch/root-ca.pem -cert /etc/opensearch/kirk.pem -key /etc/opensearch/kirk-key.pem -h <private-ip>
+sudo ./securityadmin.sh -cd {{site.url}}{{site.baseurl}}/securityconfig/ -icl -nhnv -cacert /etc/opensearch/root-ca.pem -cert /etc/opensearch/kirk.pem -key /etc/opensearch/kirk-key.pem -h <private-ip>
 ```
 
-For full guidance around configuration options, see [Security configuration](../../security/configuration).
+For full guidance around configuration options, see [Security configuration]({{site.url}}{{site.baseurl}}/security-plugin/configuration/index/).

_opensearch/common-parameters.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Common REST Parameters
-parent: OpenSearch
 nav_order: 93
 ---
 

_opensearch/configuration.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Configuration
-parent: OpenSearch
 nav_order: 5
 ---
 
@@ -9,10 +8,10 @@ nav_order: 5
 
 Most OpenSearch configuration can take place in the cluster settings API. Certain operations require you to modify `opensearch.yml` and restart the cluster.
 
-Whenever possible, use the cluster settings API instead; `opensearch.yml` is local to each node, whereas the API applies the setting to all nodes in the cluster.
+Whenever possible, use the cluster settings API instead; `opensearch.yml` is local to each node, whereas the API applies the setting to all nodes in the cluster. Certain settings, however, require `opensearch.yml`. In general, these settings relate to networking, cluster formation, and the local file system. To learn more, see [Cluster formation]({{site.url}}{{site.baseurl}}/opensearch/cluster/).
 
 
-## Cluster settings API
+## Update cluster settings using the API
 
 The first step in changing a setting is to view the current settings:
 
@@ -38,7 +37,7 @@ If you specify the same setting in multiple places, OpenSearch uses the followin
 To change a setting, just specify the new one as either persistent or transient. This example shows the flat settings form:
 
 ```json
-PUT /_cluster/settings
+PUT _cluster/settings
 {
   "persistent" : {
     "action.auto_create_index" : false
@@ -49,7 +48,7 @@ PUT /_cluster/settings
 You can also use the expanded form, which lets you copy and paste from the GET response and change existing values:
 
 ```json
-PUT /_cluster/settings
+PUT _cluster/settings
 {
   "persistent": {
     "action": {
@@ -64,6 +63,6 @@ PUT /_cluster/settings
 
 ## Configuration file
 
-You can find `opensearch.yml` in `/usr/share/opensearch/config/opensearch.yml` (Docker) or `/etc/opensearch/opensearch.yml` (RPM and DEB) on each node.
+You can find `opensearch.yml` in `/usr/share/opensearch/config/opensearch.yml` (Docker) or `/etc/opensearch/opensearch.yml` (most Linux distributions) on each node.
 
-The demo configuration includes a number of settings for the security plugin that you should modify before using OpenSearch for a production workload. To learn more, see [Security](../../security/).
+The demo configuration includes a number of settings for the security plugin that you should modify before using OpenSearch for a production workload. To learn more, see [Security]({{site.url}}{{site.baseurl}}/security-plugin/).

_opensearch/data-streams.md

@@ -0,0 +1,301 @@
+---
+layout: default
+title: Data streams
+nav_order: 13
+---
+
+# Data streams
+
+If you're ingesting continuously generated time-series data such as logs, events, and metrics into OpenSearch, you're likely in a scenario where:
+
+- You’re ingesting documents that grow rapidly.
+- You don’t need to update older documents.
+- Your searches generally target the newer documents.
+
+A typical workflow to manage time-series data is as follows:
+
+- To split your data into an index for each day, use the rollover operation.
+- To perform searches on a virtual index name that gets expanded to the underlying indices, create an [index alias]({{site.url}}{{site.baseurl}}/opensearch/index-alias/).
+- To perform a write operation on an index alias, configure the latest index as the write index.
+- To configure new indices, extract common mappings and settings into an [index template]({{site.url}}{{site.baseurl}}/opensearch/index-templates/)).
+
+Even after you perform all these operations, you’re still not enforcing the best practices when dealing with time-series data. For example, you can modify the indices directly. You’re able to ingest documents without a timestamp field, which might result in slower queries.
+
+Data streams abstract the complexity and enforce the best practices for managing time-series data.
+
+With data streams, you can store append-only time-series data across multiple indices with a single endpoint for ingesting and searching data. It replaces index aliases for time-series data.
+
+## About data streams
+
+A data stream consists of one or more hidden auto-generated backing indices. These backing indices are named using the following convention:
+
+```
+.ds-<data-stream-name>-<generation-id>
+```
+
+For example, `.ds-logs-redis-000003`, where generation-id is a six-digit, zero-padded integer that acts as a cumulative count of the data stream’s rollovers, starting at `000001`.
+
+The most recently created backing index is the data stream’s write index. You can’t add documents directly to any of the backing indices. You can only add them via the data stream handle:
+
+![data stream indexing diagram]({{site.url}}{{site.baseurl}}/images/data_stream_indexing.png)
+
+The data stream routes search requests to all of its backing indices. It uses the timestamp field to intelligently route search requests to the right set of indices and shards:
+
+![data stream indexing diagram]({{site.url}}{{site.baseurl}}/images/data_stream_searching.png)
+
+The following operations are not supported on the write index because they might hinder the indexing operation:
+
+- close
+- clone
+- delete
+- shrink
+- split
+
+## Get started with data streams
+
+### Step 1: Create an index template
+
+To create a data stream, you first need to create an index template that configures a set of indices as a data stream. The `data_stream` object indicates that it’s a data stream and not a regular index template. The index pattern matches with the name of the data stream:
+
+```json
+PUT _index_template/logs-template
+{
+  "index_patterns": [
+    "my-data-stream",
+    "logs-*"
+  ],
+  "data_stream": {},
+  "priority": 100
+}
+```
+
+In this case, each ingested document must have an `@timestamp` field.
+You also have the ability to define your own custom timestamp field as a property in the `data_stream` object. You can also add index mappings and other settings here, just as you would for a regular index template.
+
+```json
+PUT _index_template/logs-template-nginx
+{
+  "index_patterns": "logs-nginx",
+  "data_stream": {
+    "timestamp_field": {
+      "name": "request_time"
+    }
+  },
+  "priority": 200,
+  "template": {
+    "settings": {
+      "number_of_shards": 1,
+      "number_of_replicas": 0
+    }
+  }
+}
+```
+
+In this case, `logs-nginx` index matches both the `logs-template` and `logs-template-nginx` templates. When you have a tie, OpenSearch selects the matching index template with the higher priority value.
+
+### Step 2: Create a data stream
+
+After you create an index template, you can create a data stream.
+You can use the data stream API to explicitly create a data stream. The data stream API initializes the first backing index:
+
+```json
+PUT _data_stream/logs-redis
+PUT _data_stream/logs-nginx
+```
+
+You can also directly start ingesting data without creating a data stream.
+
+Because we have a matching index template with a data_stream object, OpenSearch automatically creates the data stream:
+
+```json
+POST logs-staging/_doc
+{
+  "message": "login attempt failed",
+  "@timestamp": "2013-03-01T00:00:00"
+}
+```
+
+To see information about a specific data stream:
+
+```json
+GET _data_stream/logs-nginx
+```
+
+#### Sample response
+
+```json
+{
+  "data_streams" : [
+    {
+      "name" : "logs-nginx",
+      "timestamp_field" : {
+        "name" : "request_time"
+      },
+      "indices" : [
+        {
+          "index_name" : ".ds-logs-nginx-000001",
+          "index_uuid" : "-VhmuhrQQ6ipYCmBhn6vLw"
+        }
+      ],
+      "generation" : 1,
+      "status" : "GREEN",
+      "template" : "logs-template-nginx"
+    }
+  ]
+}
+```
+
+You can see the name of the timestamp field, the list of the backing indices, and the template that's used to create the data stream. You can also see the health of the data stream, which represents the lowest status of all its backing indices.
+
+To see more insights about the data stream, use the `_stats` endpoint:
+
+```json
+GET _data_stream/logs-nginx/_stats
+```
+
+#### Sample response
+
+```json
+{
+  "_shards" : {
+    "total" : 1,
+    "successful" : 1,
+    "failed" : 0
+  },
+  "data_stream_count" : 1,
+  "backing_indices" : 1,
+  "total_store_size_bytes" : 208,
+  "data_streams" : [
+    {
+      "data_stream" : "logs-nginx",
+      "backing_indices" : 1,
+      "store_size_bytes" : 208,
+      "maximum_timestamp" : 0
+    }
+  ]
+}
+```
+
+### Step 3: Ingest data into the data stream
+
+To ingest data into a data stream, you can use the regular indexing APIs. Make sure every document that you index has a timestamp field. If you try to ingest a document that doesn't have a timestamp field, you get an error.
+
+```json
+POST logs-redis/_doc
+{
+  "message": "login attempt",
+  "@timestamp": "2013-03-01T00:00:00"
+}
+```
+
+### Step 4: Searching a data stream
+
+You can search a data stream just like you search a regular index or an index alias.
+The search operation applies to all of the backing indices (all data present in the stream).
+
+```json
+GET logs-redis/_search
+{
+  "query": {
+    "match": {
+      "message": "login"
+    }
+  }
+}
+```
+
+#### Sample response
+
+```json
+{
+  "took" : 514,
+  "timed_out" : false,
+  "_shards" : {
+    "total" : 5,
+    "successful" : 5,
+    "skipped" : 0,
+    "failed" : 0
+  },
+  "hits" : {
+    "total" : {
+      "value" : 1,
+      "relation" : "eq"
+    },
+    "max_score" : 0.2876821,
+    "hits" : [
+      {
+        "_index" : ".ds-logs-redis-000001",
+        "_type" : "_doc",
+        "_id" : "-rhVmXoBL6BAVWH3mMpC",
+        "_score" : 0.2876821,
+        "_source" : {
+          "message" : "login attempt",
+          "@timestamp" : "2013-03-01T00:00:00"
+        }
+      }
+    ]
+  }
+}
+```
+
+### Step 5: Rollover a data stream
+
+A rollover operation creates a new backing index that becomes the data stream’s new write index.
+
+To perform manual rollover operation on the data stream:
+
+```json
+POST logs-redis/_rollover
+```
+
+#### Sample response
+
+```json
+{
+  "acknowledged" : true,
+  "shards_acknowledged" : true,
+  "old_index" : ".ds-logs-redis-000001",
+  "new_index" : ".ds-logs-redis-000002",
+  "rolled_over" : true,
+  "dry_run" : false,
+  "conditions" : { }
+}
+```
+
+If you now perform a `GET` operation on the `logs-redis` data stream, you see that the generation ID is incremented from 1 to 2.
+
+You can also set up an [Index State Management (ISM) policy]({{site.url}}{{site.baseurl}}/ism/policies/) to automate the rollover process for the data stream.  
+The ISM policy is applied to the backing indices at the time of their creation. When you associate a policy to a data stream, it only affects the future backing indices of that data stream.
+
+You also don’t need to provide the `rollover_alias` setting, because the ISM policy infers this information from the backing index.
+
+### Step 6: Manage data streams in OpenSearch Dashboards
+
+To manage data streams from OpenSearch Dashboards, open **OpenSearch Dashboards**, choose **Index Management**, select **Indices** or **Policy managed indices**.
+
+You see a toggle switch for data streams that you can use to show or hide indices belonging to a data stream.
+
+When you enable this switch, you see a data stream multi-select dropdown menu that you can use for filtering data streams.
+You also see a data stream column that shows you the name of the parent data stream the index is contained in.
+
+![data stream toggle]({{site.url}}{{site.baseurl}}/images/data_streams_toggle.png)
+
+You can select one or more data streams and apply an ISM policy on them. You can also apply a policy on any individual backing index.
+
+You can performing visualizations on a data stream just like you would on a regular index or index alias.
+
+### Step 7: Delete a data stream
+
+The delete operation first deletes the backing indices of a data stream and then deletes the data stream itself.
+
+To delete a data stream and all of its hidden backing indices:
+
+```json
+DELETE _data_stream/<name_of_data_stream>
+```
+
+You can use wildcards to delete more than one data stream.
+
+We recommend deleting data from a data stream using an ISM policy.
+
+You can also use [asynchronous search]({{site.url}}{{site.baseurl}}/async/index/) and [SQL]({{site.url}}{{site.baseurl}}/sql/index/) and [PPL]({{site.url}}{{site.baseurl}}/ppl/index/) to query your data stream directly. You can also use the security plugin to define granular permissions on the data stream name.

_opensearch/index-alias.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Index aliases
-parent: OpenSearch
 nav_order: 12
 ---
 

_opensearch/index-data.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Index data
-parent: OpenSearch
 nav_order: 10
 ---
 

_opensearch/index-templates.md

@@ -0,0 +1,407 @@
+---
+layout: default
+title: Index templates
+nav_order: 15
+---
+
+# Index templates
+
+Index templates let you initialize new indices with predefined mappings and settings. For example, if you continuously index log data, you can define an index template so that all of these indices have the same number of shards and replicas.
+
+### Create a template
+
+To create an index template, use a POST request:
+
+```json
+POST _index_template
+```
+
+This command creates a template named `daily_logs` and applies it to any new index whose name matches the regular expression `logs-2020-01-*` and also adds it to the `my_logs` alias:
+
+```json
+PUT _index_template/daily_logs
+{
+  "index_patterns": [
+    "logs-2020-01-*"
+  ],
+  "template": {
+    "aliases": {
+      "my_logs": {}
+    },
+    "settings": {
+      "number_of_shards": 2,
+      "number_of_replicas": 1
+    },
+    "mappings": {
+      "properties": {
+        "timestamp": {
+          "type": "date",
+          "format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd||epoch_millis"
+        },
+        "value": {
+          "type": "double"
+        }
+      }
+    }
+  }
+}
+```
+
+You should see the following response:
+
+```json
+{
+  "acknowledged": true
+}
+```
+
+If you create an index named `logs-2020-01-01`, you can see that it has the mappings and settings from the template:
+
+```json
+PUT logs-2020-01-01
+GET logs-2020-01-01
+```
+
+```json
+{
+  "logs-2020-01-01": {
+    "aliases": {
+      "my_logs": {}
+    },
+    "mappings": {
+      "properties": {
+        "timestamp": {
+          "type": "date",
+          "format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd||epoch_millis"
+        },
+        "value": {
+          "type": "double"
+        }
+      }
+    },
+    "settings": {
+      "index": {
+        "creation_date": "1578107970779",
+        "number_of_shards": "2",
+        "number_of_replicas": "1",
+        "uuid": "U1vMDMOHSAuS2IzPcPHpOA",
+        "version": {
+          "created": "7010199"
+        },
+        "provided_name": "logs-2020-01-01"
+      }
+    }
+  }
+}
+```
+
+Any additional indices that match this pattern---`logs-2020-01-02`, `logs-2020-01-03`, and so on---will inherit the same mappings and settings.
+
+### Retrieve a template
+
+To list all index templates:
+
+```json
+GET _cat/templates
+```
+
+To find a template by its name:
+
+```json
+GET _index_template/daily_logs
+```
+
+To get a list of all your templates:
+
+```json
+GET _index_template/daily_logs
+```
+
+To get a list of all templates that match a pattern:
+
+```json
+GET _index_template/daily*
+```
+
+To check if a specific template exists:
+
+```json
+HEAD _index_template/<name>
+```
+
+### Configure multiple templates
+
+You can create multiple index templates for your indices. If the index name matches more than one template, OpenSearch merges all mappings and settings from all matching templates and applies them to the index.
+
+The settings from the more recently created index templates override the settings of older index templates. So, you can first define a few common settings in a generic template that can act as a catch-all and then add more specialized settings as required.
+
+An even better approach is to explicitly specify template priority using the `order` parameter. OpenSearch applies templates with lower priority numbers first and then overrides them with templates with higher priority numbers.
+
+For example, say you have the following two templates that both match the `logs-2020-01-02` index and there’s a conflict in the `number_of_shards` field:
+
+#### Template 1
+
+```json
+PUT _index_template/template-01
+{
+  "index_patterns": [
+    "logs*"
+  ],
+  "priority": 0,
+  "template": {
+    "settings": {
+      "number_of_shards": 2
+    }
+  }
+}
+```
+
+#### Template 2
+
+```json
+PUT _index_template/template-02
+{
+  "index_patterns": [
+    "logs-2020-01-*"
+  ],
+  "priority": 1,
+  "template": {
+    "settings": {
+      "number_of_shards": 3
+    }
+  }
+}
+```
+
+Because `template-02` has a higher `priority` value, it takes precedence over `template-01` . The `logs-2020-01-02` index would have the `number_of_shards` value as 3.
+
+### Delete a template
+
+You can delete an index template using its name:
+
+```json
+DELETE _index_template/daily_logs
+```
+
+## Composable index templates
+
+Managing multiple index templates has the following challenges:
+
+- If you have duplication between index templates, storing these index templates results in a bigger cluster state.
+- If you want to make a change across all your index templates, you have to manually make the change for each template.
+- If an index matches multiple templates, OpenSearch might merge the templates in an unexpected way that you discover only after an index is created.
+
+You can use composable index templates to overcome these challenges. Composable index templates let you abstract common settings, mappings, and aliases into a reusable building block called a component template.
+
+You can combine component templates to compose an index template.
+
+Settings and mappings that you specify directly in the [create index]({{site.url}}{{site.baseurl}}/opensearch/rest-api/create-index/) request override any settings or mappings specified in an index template and its component templates.
+{: .note }
+
+### Create a component template
+
+Let's define two component templates⁠---`component_template_1` and `component_template_2`:
+
+#### Component template 1
+
+```json
+PUT _component_template/component_template_1
+{
+  "template": {
+    "mappings": {
+      "properties": {
+        "@timestamp": {
+          "type": "date"
+        }
+      }
+    }
+  }
+}
+```
+
+#### Component template 2
+
+```json
+PUT _component_template/component_template_2
+{
+  "template": {
+    "mappings": {
+      "properties": {
+        "ip_address": {
+          "type": "ip"
+        }
+      }
+    }
+  }
+}
+```
+
+### Use component templates to create an index template
+
+When creating index templates, you need to include the component templates in a `composed_of` list.
+
+OpenSearch applies the component templates in the order in which you specify them within the index template. The settings, mappings, and aliases that you specify inside the index template are applied last.
+
+```json
+PUT _index_template/daily_logs
+{
+  "index_patterns": [
+    "logs-2020-01-*"
+  ],
+  "template": {
+    "aliases": {
+      "my_logs": {}
+    },
+    "settings": {
+      "number_of_shards": 2,
+      "number_of_replicas": 1
+    },
+    "mappings": {
+      "properties": {
+        "timestamp": {
+          "type": "date",
+          "format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd||epoch_millis"
+        },
+        "value": {
+          "type": "double"
+        }
+      }
+    }
+  },
+  "priority": 200,
+  "composed_of": [
+    "component_template_1",
+    "component_template_2"
+  ],
+  "version": 3,
+  "_meta": {
+    "description": "using component templates"
+  }
+}
+```
+
+If you create an index named `logs-2020-01-01`, you can see that it derives its mappings and settings from both the component templates:
+
+```json
+PUT logs-2020-01-01
+GET logs-2020-01-01
+```
+
+#### Sample response
+
+```json
+{
+  "logs-2020-01-01": {
+    "aliases": {
+      "my_logs": {}
+    },
+    "mappings": {
+      "properties": {
+        "@timestamp": {
+          "type": "date"
+        },
+        "ip_address": {
+          "type": "ip"
+        },
+        "timestamp": {
+          "type": "date",
+          "format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd||epoch_millis"
+        },
+        "value": {
+          "type": "double"
+        }
+      }
+    },
+    "settings": {
+      "index": {
+        "creation_date": "1625382479459",
+        "number_of_shards": "2",
+        "number_of_replicas": "1",
+        "uuid": "rYUlpOXDSUSuZifQLPfa5A",
+        "version": {
+          "created": "7100299"
+        },
+        "provided_name": "logs-2020-01-01"
+      }
+    }
+  }
+}
+```
+
+### Simulate multi-component templates
+
+For index templates composed of multiple component templates, you can simulate applying a new template to verify whether the settings are applied as you expect.
+
+To simulate the settings that would be applied to a specific index name:
+
+```json
+POST _index_template/_simulate_index/<index_name>
+```
+
+To simulate the settings that would be applied from an existing template:
+
+```json
+POST _index_template/_simulate/<index_template>
+```
+
+You can also specify a template definition in the simulate request:
+
+```json
+POST _index_template/_simulate
+{
+  "index_patterns": [
+    "logs-2020-01-*"
+  ],
+  "template": {
+    "settings" : {
+        "index.number_of_shards" : 3
+    }
+  },
+  "composed_of": ["component_template_1", "component_template_2"]
+}
+```
+
+The `_simulate` API returns the final settings, mappings, and aliases that will be applied to indices that match the index pattern. You can also see any overlapping templates whose configuration is superseded by the simulated template body or higher priority templates:
+
+```json
+{
+  "template" : {
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "3"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "@timestamp" : {
+          "type" : "date"
+        },
+        "ip_address" : {
+          "type" : "ip"
+        }
+      }
+    },
+    "aliases" : { }
+  },
+  "overlapping" : [
+    {
+      "name" : "daily_logs",
+      "index_patterns" : [
+        "logs-2020-01-*"
+      ]
+    }
+  ]
+}
+```
+
+## Index template options
+
+You can specify the following template options:
+
+Option | Type | Description | Required
+:--- | :--- | :--- | :---
+`template` | `Object` |  Specify index settings, mappings, and aliases. | No
+`priority` | `Integer` | The priority of the index template.  | No
+`composed_of` | `String array` |  The names of component templates applied on a new index together with the current template.  | No
+`version` | `Integer` | Specify a version number to simplify template management. Default is `null`. | No
+`_meta ` | `Object` | Specify meta information about the template. | No

_opensearch/index.md

@@ -1,18 +1,20 @@
 ---
 layout: default
-title: OpenSearch
-nav_order: 10
-has_children: true
+title: About OpenSearch
+nav_order: 1
+has_children: false
 has_toc: false
+redirect_from:
+  - /opensearch/
 ---
 
 # Introduction to OpenSearch
 
 OpenSearch is a distributed search and analytics engine based on [Apache Lucene](https://lucene.apache.org/). After adding your data to OpenSearch, you can perform full-text searches on it with all of the features you might expect: search by field, search multiple indices, boost fields, rank results by score, sort results by field, and aggregate results.
 
-Unsurprisingly, people often use OpenSearch as the backend for a search application---think [Wikipedia](https://en.wikipedia.org/wiki/Wikipedia:FAQ/Technical#What_software_is_used_to_run_Wikipedia?) or an online store. It offers excellent performance and can scale up and down as the needs of the application grow or shrink.
+Unsurprisingly, people often use search engines like OpenSearch as the backend for a search application---think [Wikipedia](https://en.wikipedia.org/wiki/Wikipedia:FAQ/Technical#What_software_is_used_to_run_Wikipedia?) or an online store. It offers excellent performance and can scale up and down as the needs of the application grow or shrink.
 
-An equally popular, but less obvious use case is log analytics, in which you take the logs from an application, feed them into OpenSearch, and use the rich search and visualization functionality to identify issues. For example, a malfunctioning web server might throw a 500 error 0.5% of the time, which can be hard to notice unless you have a real-time graph of all HTTP status codes that the server has thrown in the past four hours. You can use [OpenSearch Dashboards](../opensearch-dashboards/) to build these sorts of visualizations from data in OpenSearch.
+An equally popular, but less obvious use case is log analytics, in which you take the logs from an application, feed them into OpenSearch, and use the rich search and visualization functionality to identify issues. For example, a malfunctioning web server might throw a 500 error 0.5% of the time, which can be hard to notice unless you have a real-time graph of all HTTP status codes that the server has thrown in the past four hours. You can use [OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/) to build these sorts of visualizations from data in OpenSearch.
 
 
 ## Clusters and nodes
@@ -21,7 +23,7 @@ Its distributed design means that you interact with OpenSearch *clusters*. Each
 
 You can run OpenSearch locally on a laptop---its system requirements are minimal---but you can also scale a single cluster to hundreds of powerful machines in a data center.
 
-In a single node cluster, such as a laptop, one machine has to do everything: manage the state of the cluster, index and search data, and perform any preprocessing of data prior to indexing it. As a cluster grows, however, you can subdivide responsibilities. Nodes with fast disks and plenty of RAM might be great at indexing and searching data, whereas a node with plenty of CPU power and a tiny disk could manage cluster state. For more information on setting node types, see [Cluster formation](cluster/).
+In a single node cluster, such as a laptop, one machine has to do everything: manage the state of the cluster, index and search data, and perform any preprocessing of data prior to indexing it. As a cluster grows, however, you can subdivide responsibilities. Nodes with fast disks and plenty of RAM might be great at indexing and searching data, whereas a node with plenty of CPU power and a tiny disk could manage cluster state. For more information on setting node types, see [Cluster formation]({{site.url}}{{site.baseurl}}/opensearch/cluster/).
 
 
 ## Indices and documents

_opensearch/install/compatibility.md

@@ -0,0 +1,19 @@
+---
+layout: default
+title: Compatibility
+parent: Install OpenSearch
+nav_order: 2
+---
+
+# Operating system and JVM compatibility
+
+- We recommend installing OpenSearch on RHEL- or Debian-based Linux distributions that use [systemd](https://en.wikipedia.org/wiki/Systemd), such as CentOS, Amazon Linux 2, and Ubuntu (LTS). OpenSearch should work on many Linux distributions, but we only test a handful.
+- The OpenSearch tarball ships with a compatible version of Java in the `jdk` directory. To find its version, run `./jdk/bin/java -version`. For example, the OpenSearch 1.0.0 tarball ships with Java 15 (non-LTS).
+
+{% comment %}`./jdk/bin/java -version` doesn't work on macOS with zsh at the moment, and I have no idea why. Maybe we need a macOS artifact. Regardless, the command works on Amazon Linux 2 with bash and presumably other distros. - aetter{% endcomment %}
+
+  To use a different Java installation, set the `OPENSEARCH_JAVA_HOME` environment variable to the Java install location. We recommend Java 11 (LTS), but OpenSearch also works with Java 8.
+
+OpenSearch version | Compatible Java versions | Recommended operating systems
+:--- | :--- | :---
+1.x | 8, 11 | Red Hat Enterprise Linux 7, 8; CentOS 7, 8; Amazon Linux 2; Ubuntu 16.04, 18.04, 20.04

_opensearch/install/docker-security.md

@@ -2,16 +2,16 @@
 layout: default
 title: Docker security configuration
 parent: Install OpenSearch
-grand_parent: OpenSearch
 nav_order: 5
 ---
 
 # Docker security configuration
 
-Before deploying to a production environment, you should replace the demo security certificates and configuration YAML files with your own. With the tarball, you have direct access to the file system, but the Docker image requires modifying the Docker storage volumes include the replacement files.
+Before deploying to a production environment, you should replace the demo security certificates and configuration YAML files with your own. With the tarball, you have direct access to the file system, but the Docker image requires modifying the Docker storage volumes to include the replacement files.
 
 Additionally, you can set the Docker environment variable `DISABLE_INSTALL_DEMO_CONFIG` to `true`. This change completely disables the demo installer.
 
+
 ## Sample Docker Compose file
 
 ```yml
@@ -94,8 +94,7 @@ services:
     expose:
       - "5601"
     environment:
-      OPENSEARCH_URL: https://opensearch-node1:9200
-      OPENSEARCH_HOSTS: https://opensearch-node1:9200
+      OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]' # must be a string with no spaces when specified as an environment variable
     volumes:
       - ./custom-opensearch_dashboards.yml:/usr/share/opensearch-dashboards/config/opensearch_dashboards.yml
     networks:
@@ -109,32 +108,32 @@ networks:
   opensearch-net:
 ```
 
-Then make your changes to `opensearch.yml`. For a full list of settings, see [Security](../../../security/configuration/). This example adds (extremely) verbose audit logging:
+Then make your changes to `opensearch.yml`. For a full list of settings, see [Security]({{site.url}}{{site.baseurl}}/security-plugin/configuration/index/). This example adds (extremely) verbose audit logging:
 
 ```yml
-opensearch_security.ssl.transport.pemcert_filepath: node.pem
-opensearch_security.ssl.transport.pemkey_filepath: node-key.pem
-opensearch_security.ssl.transport.pemtrustedcas_filepath: root-ca.pem
-opensearch_security.ssl.transport.enforce_hostname_verification: false
-opensearch_security.ssl.http.enabled: true
-opensearch_security.ssl.http.pemcert_filepath: node.pem
-opensearch_security.ssl.http.pemkey_filepath: node-key.pem
-opensearch_security.ssl.http.pemtrustedcas_filepath: root-ca.pem
-opensearch_security.allow_default_init_securityindex: true
-opensearch_security.authcz.admin_dn:
+plugins.security.ssl.transport.pemcert_filepath: node.pem
+plugins.security.ssl.transport.pemkey_filepath: node-key.pem
+plugins.security.ssl.transport.pemtrustedcas_filepath: root-ca.pem
+plugins.security.ssl.transport.enforce_hostname_verification: false
+plugins.security.ssl.http.enabled: true
+plugins.security.ssl.http.pemcert_filepath: node.pem
+plugins.security.ssl.http.pemkey_filepath: node-key.pem
+plugins.security.ssl.http.pemtrustedcas_filepath: root-ca.pem
+plugins.security.allow_default_init_securityindex: true
+plugins.security.authcz.admin_dn:
   - CN=A,OU=UNIT,O=ORG,L=TORONTO,ST=ONTARIO,C=CA
-opensearch_security.nodes_dn:
+plugins.security.nodes_dn:
   - 'CN=N,OU=UNIT,O=ORG,L=TORONTO,ST=ONTARIO,C=CA'
-opensearch_security.audit.type: internal_opensearch
-opensearch_security.enable_snapshot_restore_privilege: true
-opensearch_security.check_snapshot_restore_write_privileges: true
-opensearch_security.restapi.roles_enabled: ["all_access", "security_rest_api_access"]
+plugins.security.audit.type: internal_opensearch
+plugins.security.enable_snapshot_restore_privilege: true
+plugins.security.check_snapshot_restore_write_privileges: true
+plugins.security.restapi.roles_enabled: ["all_access", "security_rest_api_access"]
 cluster.routing.allocation.disk.threshold_enabled: false
-opensearch_security.audit.config.disabled_rest_categories: NONE
-opensearch_security.audit.config.disabled_transport_categories: NONE
+plugins.security.audit.config.disabled_rest_categories: NONE
+plugins.security.audit.config.disabled_transport_categories: NONE
 ```
 
-Use this same override process to specify new [authentication settings](../../../security/configuration/configuration/) in `/usr/share/opensearch/plugins/opensearch-security/securityconfig/config.yml`, as well as new default [internal users, roles, mappings, action groups, and tenants](../../../security/configuration/yaml/).
+Use this same override process to specify new [authentication settings]({{site.url}}{{site.baseurl}}/security-plugin/configuration/configuration/) in `/usr/share/opensearch/plugins/opensearch-security/securityconfig/config.yml`, as well as new default [internal users, roles, mappings, action groups, and tenants]({{site.url}}{{site.baseurl}}/security-plugin/configuration/yaml/).
 
 To start the cluster, run `docker-compose up`.
 
@@ -143,6 +142,7 @@ If you encounter any `File /usr/share/opensearch/config/opensearch.yml has insec
 
 Finally, you can reach OpenSearch Dashboards at http://localhost:5601, sign in, and use the **Security** panel to perform other management tasks.
 
+
 ## Using certificates with Docker
 
 To use your own certificates in your configuration, add all of the necessary certificates to the volumes section of the Docker Compose file:
@@ -163,16 +163,16 @@ volumes:
 - ./custom-opensearch.yml: /full/path/to/custom-opensearch.yml
 ```
 
-Remember that the certificates you specify in your Docker Compose file must be the same as the certificates listed in your custom `opensearch.yml` file. At a minimum, you should replace the root, admin, and node certificates with your own. For more information about adding and using certificates, see [Configure TLS certificates](../security/configuration/tls.md).
+Remember that the certificates you specify in your Docker Compose file must be the same as the certificates listed in your custom `opensearch.yml` file. At a minimum, you should replace the root, admin, and node certificates with your own. For more information about adding and using certificates, see [Configure TLS certificates]({{site.url}}{{site.baseurl}}/security-plugin/configuration/tls).
 
 ```yml
-opensearch_security.ssl.transport.pemcert_filepath: new-node-cert.pem
-opensearch_security.ssl.transport.pemkey_filepath: new-node-cert-key.pem
-opensearch_security.ssl.transport.pemtrustedcas_filepath: new-root-ca.pem
-opensearch_security.ssl.http.pemcert_filepath: new-node-cert.pem
-opensearch_security.ssl.http.pemkey_filepath: new-node-cert-key.pem
-opensearch_security.ssl.http.pemtrustedcas_filepath: new-root-ca.pem
-opensearch_security.authcz.admin_dn:
+plugins.security.ssl.transport.pemcert_filepath: new-node-cert.pem
+plugins.security.ssl.transport.pemkey_filepath: new-node-cert-key.pem
+plugins.security.ssl.transport.pemtrustedcas_filepath: new-root-ca.pem
+plugins.security.ssl.http.pemcert_filepath: new-node-cert.pem
+plugins.security.ssl.http.pemkey_filepath: new-node-cert-key.pem
+plugins.security.ssl.http.pemtrustedcas_filepath: new-root-ca.pem
+plugins.security.authcz.admin_dn:
   - CN=admin,OU=SSL,O=Test,L=Test,C=DE
 ```
 

_opensearch/install/docker.md

@@ -2,8 +2,7 @@
 layout: default
 title: Docker
 parent: Install OpenSearch
-grand_parent: OpenSearch
-nav_order: 1
+nav_order: 3
 ---
 
 # Docker image
@@ -17,7 +16,7 @@ docker pull opensearchproject/opensearch-dashboards:{{site.opensearch_version}}
 
 To check available versions, see [Docker Hub](https://hub.docker.com/u/opensearchproject).
 
-OpenSearch images use `centos:7` as the base image. If you run Docker locally, we recommend allowing Docker to use at least 4 GB of RAM in **Preferences** > **Resources**.
+OpenSearch images use `amazonlinux:2` as the base image. If you run Docker locally, set Docker to use at least 4 GB of RAM in **Preferences** > **Resources**.
 
 
 ---
@@ -139,7 +138,7 @@ services:
     expose:
       - "5601"
     environment:
-      OPENSEARCH_HOSTS: https://opensearch-node1:9200
+      OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]' # must be a string with no spaces when specified as an environment variable
     networks:
       - opensearch-net
 
@@ -151,13 +150,13 @@ networks:
   opensearch-net:
 ```
 
-If you override `opensearch_dashboards.yml` settings using environment variables, as seen above, use all uppercase letters and periods in place of underscores (e.g. for `opensearch.url`, specify `OPENSEARCH_URL`).
+If you override `opensearch_dashboards.yml` settings using environment variables, as seen above, use all uppercase letters and periods in place of underscores (e.g. for `opensearch.hosts`, use `OPENSEARCH_HOSTS`).
 {: .note}
 
 
 ## Configure OpenSearch
 
-You can pass a custom `opensearch.yml` file to the Docker container using the [`-v` flag](https://docs.docker.com/engine/reference/commandline/run/#mount-volume--v---read-only) for `docker run`:
+You can pass a custom `opensearch.yml` file to the Docker container using the [`-v` flag](https://docs.docker.com/engine/reference/commandline/run#mount-volume--v---read-only) for `docker run`:
 
 ```bash
 docker run \
@@ -184,7 +183,7 @@ services:
       - ./custom-opensearch_dashboards.yml:/usr/share/opensearch-dashboards/config/opensearch_dashboards.yml
 ```
 
-You can also configure `docker-compose.yml` and `opensearch.yml` [to take your own certificates](../docker-security/) for use with the [Security](../../security/configuration/) plugin.
+You can also configure `docker-compose.yml` and `opensearch.yml` [to take your own certificates]({{site.url}}{{site.baseurl}}/opensearch/install/docker-security/) for use with the [Security]({{site.url}}{{site.baseurl}}/security-plugin/configuration/index/) plugin.
 
 
 ### (Optional) Set up Performance Analyzer
@@ -192,25 +191,25 @@ You can also configure `docker-compose.yml` and `opensearch.yml` [to take your o
 1. Enable the Performance Analyzer plugin:
 
    ```bash
-   curl -XPOST localhost:9200/_opensearch/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
+   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
    ```
 
    If you receive the `curl: (52) Empty reply from server` error, you are likely protecting your cluster with the security plugin and you need to provide credentials. Modify the following command to use your username and password:
 
    ```bash
-   curl -XPOST https://localhost:9200/_opensearch/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
+   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
    ```
 
 1. Enable the Root Cause Analyzer (RCA) framework
 
    ```bash
-   curl -XPOST localhost:9200/_opensearch/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
+   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
    ```
 
    Similar to step 1, if you run into `curl: (52) Empty reply from server`, run the command below to enable RCA
 
    ```bash
-   curl -XPOST https://localhost:9200/_opensearch/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
+   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
    ```
 
 1. By default, Performance Analyzer's endpoints are not accessible from outside the Docker container.
@@ -299,7 +298,7 @@ docker build --tag=opensearch-custom-plugin .
 docker run -p 9200:9200 -p 9600:9600 -v /usr/share/opensearch/data opensearch-custom-plugin
 ```
 
-You can also use a `Dockerfile` to pass your own certificates for use with the [Security](../../../security/) plugin, similar to the `-v` argument in [Configure OpenSearch](#configure-opensearch):
+You can also use a `Dockerfile` to pass your own certificates for use with the [security]({{site.url}}{{site.baseurl}}/security-plugin/) plugin, similar to the `-v` argument in [Configure OpenSearch](#configure-opensearch):
 
 ```
 FROM opensearchproject/opensearch:{{site.opensearch_version}}
@@ -313,11 +312,11 @@ Alternately, you might want to remove a plugin. This `Dockerfile` removes the se
 
 ```
 FROM opensearchproject/opensearch:{{site.opensearch_version}}
-RUN /usr/share/opensearch/bin/opensearch-plugin remove opensearch_security
+RUN /usr/share/opensearch/bin/opensearch-plugin remove opensearch-security
 COPY --chown=opensearch:opensearch opensearch.yml /usr/share/opensearch/config/
 ```
 
-In this case, `opensearch.yml` is a "vanilla" version of the file with no OpenSearch entries. It might look like this:
+In this case, `opensearch.yml` is a "vanilla" version of the file with no plugin entries. It might look like this:
 
 ```yml
 cluster.name: "docker-cluster"

_opensearch/install/important-settings.md

@@ -2,7 +2,6 @@
 layout: default
 title: Important settings
 parent: Install OpenSearch
-grand_parent: OpenSearch
 nav_order: 70
 ---
 
@@ -22,7 +21,7 @@ vm.max_map_count=262144
 
 Then run `sudo sysctl -p` to reload.
 
-The [sample docker-compose.yml](../docker/#sample-docker-compose-file) file also contains several key settings:
+The [sample docker-compose.yml]({{site.url}}{{site.baseurl}}/opensearch/install/docker#sample-docker-compose-file) file also contains several key settings:
 
 - `bootstrap.memory_lock=true`
 

_opensearch/install/index.md

@@ -1,9 +1,10 @@
 ---
 layout: default
 title: Install OpenSearch
-nav_order: 1
-parent: OpenSearch
-redirect_from: /docs/install/
+nav_order: 2
+redirect_from:
+  - /docs/install/
+  - /opensearch/install/
 has_children: true
 ---
 

_opensearch/install/plugins.md

@@ -2,7 +2,6 @@
 layout: default
 title: OpenSearch plugins
 parent: Install OpenSearch
-grand_parent: OpenSearch
 nav_order: 90
 ---
 
@@ -30,6 +29,23 @@ If you don't want to use the all-in-one OpenSearch installation options, you can
     </tr>
   </thead>
   <tbody>
+  <tr>
+    <td>1.0.0-rc1</td>
+    <td>
+      <pre>opensearch-alerting             1.0.0.0-rc1
+opensearch-anomaly-detection    1.0.0.0-rc1
+opensearch-asynchronous-search  1.0.0.0-rc1
+opensearch-index-management     1.0.0.0-rc1
+opensearch-job-scheduler        1.0.0.0-rc1
+opensearch-knn                  1.0.0.0-rc1
+opensearch-notebooks            1.0.0.0-rc1
+opensearch-performance-analyzer 1.0.0.0-rc1
+opensearch-reports-scheduler    1.0.0.0-rc1
+opensearch-security             1.0.0.0-rc1
+opensearch-sql                  1.0.0.0-rc1
+</pre>
+    </td>
+  </tr>
   <tr>
     <td>1.0.0-beta1</td>
     <td>
@@ -65,7 +81,7 @@ Then you can specify the version that you need:
 sudo yum install opensearch-oss-6.7.1
 ```
 
-{% endcomment %}
+
 
 
 ## Install plugins
@@ -79,9 +95,9 @@ Navigate to the OpenSearch home directory (most likely, it is `/usr/share/opense
 sudo bin/opensearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/opensearch-plugins/opensearch-security/opensearch-security-{{site.opensearch_major_minor_version}}.1.0.zip
 ```
 
-After installing the security plugin, you can run `sudo sh /usr/share/opensearch/plugins/opensearch-security/tools/install_demo_configuration.sh` to quickly get started with demo certificates. Otherwise, you must configure it manually and run [securityadmin.sh](../../../security/configuration/security-admin/).
+After installing the security plugin, you can run `sudo sh /usr/share/opensearch/plugins/opensearch-security/tools/install_demo_configuration.sh` to quickly get started with demo certificates. Otherwise, you must configure it manually and run [securityadmin.sh]({{site.url}}{{site.baseurl}}/security-plugin/configuration/security-admin/).
 
-The security plugin has a corresponding [OpenSearch Dashboards plugin](../../../opensearch-dashboards/install/plugins) that you probably want to install as well.
+The security plugin has a corresponding [OpenSearch Dashboards plugin]({{site.url}}{{site.baseurl}}/opensearch-dashboards/install/plugins) that you probably want to install as well.
 
 
 ### Job scheduler
@@ -97,7 +113,7 @@ sudo bin/opensearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloa
 sudo bin/opensearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/opensearch-plugins/opensearch-alerting/opensearch-alerting-{{site.opensearch_major_minor_version}}.1.0.zip
 ```
 
-To install Alerting, you must first install the Job Scheduler plugin. Alerting has a corresponding [OpenSearch Dashboards plugin](../../../opensearch-dashboards/install/plugins/) that you probably want to install as well.
+To install Alerting, you must first install the Job Scheduler plugin. Alerting has a corresponding [OpenSearch Dashboards plugin]({{site.url}}{{site.baseurl}}/opensearch-dashboards/install/plugins/) that you probably want to install as well.
 
 
 ### SQL
@@ -120,7 +136,7 @@ sudo bin/opensearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloa
 sudo bin/opensearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/opensearch-plugins/opensearch-index-management/opensearch-index-management-{{site.opensearch_major_minor_version}}.2.0.zip
 ```
 
-To install Index State Management, you must first install the Job Scheduler plugin. ISM has a corresponding [OpenSearch Dashboards plugin](../../../opensearch-dashboards/install/plugins/) that you probably want to install as well.
+To install Index State Management, you must first install the Job Scheduler plugin. ISM has a corresponding [OpenSearch Dashboards plugin]({{site.url}}{{site.baseurl}}/opensearch-dashboards/install/plugins/) that you probably want to install as well.
 
 
 ### k-NN
@@ -227,9 +243,9 @@ Performance Analyzer requires some manual configuration after installing the plu
 1. Send a test request:
 
    ```bash
-   curl -XGET "localhost:9600/_opensearch/_performanceanalyzer/metrics?metrics=Latency,CPU_Utilization&agg=avg,max&dim=ShardID&nodes=all"
+   curl -XGET "localhost:9600/_plugins/_performanceanalyzer/metrics?metrics=Latency,CPU_Utilization&agg=avg,max&dim=ShardID&nodes=all"
    ```
-
+{% endcomment %}
 
 ## List installed plugins
 

_opensearch/install/tar.md

@@ -2,7 +2,6 @@
 layout: default
 title: Tarball
 parent: Install OpenSearch
-grand_parent: OpenSearch
 nav_order: 50
 ---
 
@@ -46,7 +45,7 @@ You can modify `config/opensearch.yml` or specify environment variables as argum
 ./opensearch-tar-install.sh -Ecluster.name=opensearch-cluster -Enode.name=opensearch-node1 -Ehttp.host=0.0.0.0 -Ediscovery.type=single-node
 ```
 
-For other settings, see [Important settings](../important-settings/).
+For other settings, see [Important settings]({{site.url}}{{site.baseurl}}/opensearch/install/important-settings/).
 
 
 ### (Optional) Set up Performance Analyzer
@@ -118,31 +117,31 @@ In a tarball installation, Performance Analyzer collects data when it is enabled
 1. In a separate window, enable the Performance Analyzer plugin:
 
    ```bash
-   curl -XPOST localhost:9200/_opensearch/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
+   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
    ```
 
    If you receive the `curl: (52) Empty reply from server` error, you are likely protecting your cluster with the security plugin and you need to provide credentials. Modify the following command to use your username and password:
 
    ```bash
-   curl -XPOST https://localhost:9200/_opensearch/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
+   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
    ```
 
 1. Finally, enable the Root Cause Analyzer (RCA) framework
 
    ```bash
-   curl -XPOST localhost:9200/_opensearch/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
+   curl -XPOST localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
    ```
 
    Similar to step 4, if you run into `curl: (52) Empty reply from server`, run the command below to enable RCA
 
    ```bash
-   curl -XPOST https://localhost:9200/_opensearch/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
+   curl -XPOST https://localhost:9200/_plugins/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin' -k
    ```
 
 {% comment %}
 
 ### (Optional) Removing Performance Analyzer
 
-See [Clean up Performance Analyzer files](../plugins/#optional-clean-up-performance-analyzer-files).
+See [Clean up Performance Analyzer files]({{site.url}}{{site.baseurl}}/plugins#optional-clean-up-performance-analyzer-files).
 
 {% endcomment %}

_opensearch/logs.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Logs
-parent: OpenSearch
 nav_order: 60
 ---
 
@@ -10,9 +9,9 @@ nav_order: 60
 The OpenSearch logs include valuable information for monitoring cluster operations and troubleshooting issues. The location of the logs differs based on the installation type:
 
 - On Docker, OpenSearch writes most logs to the console and stores the remainder in `opensearch/logs/`. The tarball installation also uses `opensearch/logs/`.
-- On the RPM and Debian installations, OpenSearch writes logs to `/var/log/opensearch/`.
+- On most Linux installations, OpenSearch writes logs to `/var/log/opensearch/`.
 
-Logs are available as `.log` (plain text) and `.json` files.
+Logs are available as `.log` (plain text) and `.json` files. Permissions for the OpenSearch logs are `-rw-r--r--` by default, meaning that any user account on the node can read them. You can change this behavior _for each log type_ in `log4j2.properties` using the `filePermissions` option. For example, you might add `appender.rolling.filePermissions = rw-r-----` to change permissions for the JSON server log. For details, see the [Log4j 2 documentation](https://logging.apache.org/log4j/2.x/manual/appenders.html#RollingFileAppender).
 
 
 ## Application logs

_opensearch/metric-agg.md

@@ -2,12 +2,11 @@
 layout: default
 title: Metric Aggregations
 parent: Aggregations
-grand_parent: OpenSearch
 nav_order: 1
 has_children: false
 ---
 
-# Metric Aggregations
+# Metric aggregations
 
 Metric aggregations let you perform simple calculations such as finding the minimum, maximum, and average values of a field.
 

_opensearch/pipeline-agg.md

@@ -2,12 +2,11 @@
 layout: default
 title: Pipeline Aggregations
 parent: Aggregations
-grand_parent: OpenSearch
 nav_order: 4
 has_children: false
 ---
 
-# Pipeline Aggregations
+# Pipeline aggregations
 
 With pipeline aggregations, you can chain aggregations by piping the results of one aggregation as an input to another for a more nuanced output.
 

_opensearch/popular-api.md

@@ -1,13 +1,12 @@
 ---
 layout: default
 title: Popular APIs
-parent: OpenSearch
 nav_order: 96
 ---
 
 # Popular APIs
 
-This page contains sample requests for popular OpenSearch APIs.
+This page contains sample requests for popular OpenSearch operations.
 
 
 ---
@@ -81,7 +80,7 @@ POST _bulk
 ## List all indices
 
 ```
-GET _cat/indices?v
+GET _cat/indices?v&expand_wildcards=all
 ```
 
 
@@ -184,7 +183,7 @@ PUT _snapshot/my-repository/my-snapshot
 ```json
 POST _snapshot/my-repository/my-snapshot/_restore
 {
-  "indices": "-.opensearch_security",
+  "indices": "-.opendistro_security",
   "include_global_state": false
 }
 ```

_opensearch/query-dsl/bool.md

@@ -1,8 +1,9 @@
 ---
 layout: default
 title: Boolean queries
-parent: OpenSearch
+parent: Query DSL
 nav_order: 45
+redirect_from: /docs/opensearch/bool/
 ---
 
 # Boolean queries

_opensearch/query-dsl/full-text.md

@@ -1,14 +1,15 @@
 ---
 layout: default
 title: Full-text queries
-parent: OpenSearch
+parent: Query DSL
 nav_order: 40
+redirect_from:
+  - /docs/opensearch/full-text/
+  - /opensearch/full-text/
 ---
 
 # Full-text queries
 
-Although you can use HTTP request parameters to perform simple searches, the OpenSearch query domain-specific language (DSL) lets you specify the full range of search options. The query DSL uses the HTTP request body. Queries specified in this way have the added advantage of being more explicit in their intent and easier to tune over time.
-
 This page lists all full-text query types and common options. Given the sheer number of options and subtle behaviors, the best method of ensuring useful search results is to test different queries against representative indices and verify the output.
 
 

_opensearch/query-dsl/index.md

@@ -0,0 +1,122 @@
+---
+layout: default
+title: Query DSL
+nav_order: 27
+has_children: true
+redirect_from:
+  - /opensearch/query-dsl/
+---
+
+# Query DSL
+
+While you can use HTTP request parameters to perform simple searches, you can also use the OpenSearch query domain-specific language (DSL), which provides a wider range of search options. The query DSL uses the HTTP request body, so you can more easily customize your queries to get the exact results that you want.
+
+For example, the following request performs a simple search to search for a `speaker` field that has a value of `queen`.
+
+**Sample request**
+```json
+GET _search?q=speaker:queen
+```
+
+**Sample response**
+```
+{
+  "took": 87,
+  "timed_out": false,
+  "_shards": {
+  "total": 68,
+  "successful": 68,
+  "skipped": 0,
+  "failed": 0
+  },
+  "hits": {
+  "total": {
+    "value": 4080,
+    "relation": "eq"
+  },
+  "max_score": 4.4368687,
+  "hits": [
+    {
+    "_index": "new_shakespeare",
+    "_type": "_doc",
+    "_id": "28559",
+    "_score": 4.4368687,
+    "_source": {
+      "type": "line",
+      "line_id": 28560,
+      "play_name": "Cymbeline",
+      "speech_number": 20,
+      "line_number": "1.1.81",
+      "speaker": "QUEEN",
+      "text_entry": "No, be assured you shall not find me, daughter,"
+    }
+    }
+```
+
+With query DSL, however, you can include an HTTP request body to look for results more tailored to your needs. The following example shows how to search for `speaker` and `text_entry` fields that have a value of `QUEEN`.
+
+**Sample request**
+```json
+{
+  "query": {
+  "multi_match": {
+    "query": "QUEEN",
+    "fields": ["speaker", "text_entry"]
+    }
+  }
+}
+```
+
+**Sample Response**
+```json
+{
+  "took": 39,
+  "timed_out": false,
+  "_shards": {
+    "total": 68,
+    "successful": 68,
+    "skipped": 0,
+    "failed": 0
+  },
+  "hits": {
+    "total": {
+      "value": 5837,
+      "relation": "eq"
+    },
+    "max_score": 7.8623476,
+    "hits": [
+      {
+        "_index": "new_shakespeare",
+        "_type": "_doc",
+        "_id": "100763",
+        "_score": 7.8623476,
+        "_source": {
+          "type": "line",
+          "line_id": 100764,
+          "play_name": "Troilus and Cressida",
+          "speech_number": 43,
+          "line_number": "3.1.68",
+          "speaker": "PANDARUS",
+          "text_entry": "Sweet queen, sweet queen! thats a sweet queen, i faith."
+        }
+      },
+      {
+        "_index": "shakespeare",
+        "_type": "_doc",
+        "_id": "28559",
+        "_score": 5.8923807,
+        "_source": {
+          "type": "line",
+          "line_id": 28560,
+          "play_name": "Cymbeline",
+          "speech_number": 20,
+          "line_number": "1.1.81",
+          "speaker": "QUEEN",
+          "text_entry": "No, be assured you shall not find me, daughter,"
+        }
+      }
+    ]
+  }
+}
+```
+The OpenSearch query DSL comes in three varieties: term-level queries, full-text queries, and boolean queries. You can even perform more complicated searches by using different elements from each variety to find whatever data you need.

_opensearch/query-dsl/term.md

@@ -1,8 +1,9 @@
 ---
 layout: default
 title: Term-level queries
-parent: OpenSearch
+parent: Query DSL
 nav_order: 30
+redirect_from: /docs/opensearch/term/
 ---
 
 # Term-level queries
@@ -144,7 +145,7 @@ The search query “To be, or not to be” is analyzed and tokenized into an arr
 ...
 ```
 
-For a list of all full-text queries, see [Full-text queries](../full-text/).
+For a list of all full-text queries, see [Full-text queries]({{site.url}}{{site.baseurl}}/opensearch/full-text/).
 
 If you want to query for an exact term like “HAMLET” in the speaker field and don't need the results to be sorted by relevance scores, a term-level query is more efficient:
 

_opensearch/reindex-data.md

@@ -1,7 +1,6 @@
 ---
 layout: default
 title: Reindex data
-parent: OpenSearch
 nav_order: 16
 ---
 
@@ -113,7 +112,7 @@ POST _reindex
 }
 ```
 
-For a list of all query operations, see [Full-text queries](../full-text/).
+For a list of all query operations, see [Full-text queries]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/).
 
 ## Combine one or more indices
 

_opensearch/rest-api/cat/cat-aliases.md

@@ -0,0 +1,61 @@
+---
+layout: default
+title: cat aliases
+parent: CAT
+grand_parent: REST API reference
+nav_order: 1
+has_children: false
+---
+
+# cat aliases
+
+The cat aliases operation lists the mapping of aliases to indices, plus routing and filtering information.
+
+## Example
+
+```json
+GET _cat/aliases?v
+```
+
+To limit the information to a specific alias, add the alias name after your query:
+
+```json
+GET _cat/aliases/<alias>?v
+```
+
+If you want to get information for more than one alias, separate the alias names with commas:
+
+```json
+GET _cat/aliases/alias1,alias2,alias3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/aliases/<alias>
+GET _cat/aliases
+```
+
+
+## URL parameters
+
+All cat aliases URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+expand_wildcards | Enum | Expands wildcard expressions to concrete indices. Combine multiple values with commas. Supported values are `all`, `open`, `closed`, `hidden`, and `none`. Default is `open`.
+
+## Response
+
+The following response shows that `alias1` refers to a `movies` index and has a configured filter:
+
+```json
+alias   | index     | filter  | routing.index | routing.search  | is_write_index
+alias1  | movies    |   *     |      -        |       -         |      -
+.kibana | .kibana_1 |   -     |      -        |       -         |      -
+```
+
+To learn more about index aliases, see [Index aliases]({{site.url}}{{site.baseurl}}/opensearch/index-alias).

_opensearch/rest-api/cat/cat-allocation.md

@@ -0,0 +1,61 @@
+---
+layout: default
+title: cat allocation
+parent: CAT
+grand_parent: REST API reference
+nav_order: 5
+has_children: false
+---
+
+# cat allocation
+
+The cat allocation operation lists the allocation of disk space for indices and the number of shards on each node.
+
+## Example
+
+```json
+GET _cat/allocation?v
+```
+
+To limit the information to a specific node, add the node name after your query:
+
+```json
+GET _cat/allocation/<node_name>
+```
+
+If you want to get information for more than one node, separate the node names with commas:
+
+```json
+GET _cat/aliases/node_name_1,node_name_2,node_name_3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/allocation?v
+GET _cat/allocation/<node_name>
+```
+
+## URL parameters
+
+All cat allocation URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+bytes | Byte size | Specify the units for byte size. For example, `7kb` or `6gb`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+
+
+
+## Response
+
+The following response shows that 8 shards are allocated to each the two nodes available:
+
+```json
+shards | disk.indices | disk.used | disk.avail | disk.total | disk.percent host | ip          | node
+  8    |   989.4kb    |   25.9gb  |   32.4gb   |   58.4gb   |   44 172.18.0.4   | 172.18.0.4  | odfe-node1
+  8    |   962.4kb    |   25.9gb  |   32.4gb   |   58.4gb   |   44 172.18.0.3   | 172.18.0.3  | odfe-node2
+```

_opensearch/rest-api/cat/cat-count.md

@@ -0,0 +1,51 @@
+---
+layout: default
+title: cat count
+parent: CAT
+grand_parent: REST API reference
+nav_order: 10
+has_children: false
+---
+
+# cat count
+
+The cat count operation lists the number of documents in your cluster.
+
+## Example
+
+```json
+GET _cat/count?v
+```
+
+To see the number of documents in a specific index or alias, add the index or alias name after your query:
+
+```json
+GET _cat/count/<index_or_alias>?v
+```
+
+If you want to get information for more than one index or alias, separate the index or alias names with commas:
+
+```json
+GET _cat/aliases/index_or_alias_1,index_or_alias_2,index_or_alias_3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/count?v
+GET _cat/count/<index>?v
+```
+
+## URL parameters
+
+All cat count URL parameters are optional. You can specify any of the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters).
+
+
+## Response
+
+The following response shows the overall document count as 1625:
+
+```json
+epoch      | timestamp | count
+1624237738 | 01:08:58  | 1625
+```

_opensearch/rest-api/cat/cat-field-data.md

@@ -0,0 +1,57 @@
+---
+layout: default
+title: cat field data
+parent: CAT
+grand_parent: REST API reference
+nav_order: 15
+has_children: false
+---
+
+# cat fielddata
+
+The cat fielddata operation lists the memory size used by each field per node.
+
+## Example
+
+```json
+GET _cat/fielddata?v
+```
+
+To limit the information to a specific field, add the field name after your query:
+
+```json
+GET _cat/fielddata/<field_name>?v
+```
+
+If you want to get information for more than one field, separate the field names with commas:
+
+```json
+GET _cat/aliases/field_name_1,field_name_2,field_name_3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/fielddata?v
+GET _cat/fielddata/<field_name>?v
+```
+
+## URL parameters
+
+All cat fielddata URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameter:
+
+Parameter | Type | Description
+:--- | :--- | :---
+bytes | Byte size | Specify the units for byte size. For example, `7kb` or `6gb`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+
+## Response
+
+The following response shows the memory size for all fields as 284 bytes:
+
+```json
+id                     host       ip         node       field size
+1vo54NuxSxOrbPEYdkSF0w 172.18.0.4 172.18.0.4 odfe-node1 _id   284b
+ZaIkkUd4TEiAihqJGkp5CA 172.18.0.3 172.18.0.3 odfe-node2 _id   284b
+```

_opensearch/rest-api/cat/cat-health.md

@@ -0,0 +1,42 @@
+---
+layout: default
+title: cat health
+parent: CAT
+grand_parent: REST API reference
+nav_order: 20
+has_children: false
+---
+
+# cat health
+
+The cat health operation lists the status of the cluster, how long the cluster has been up, the number of nodes, and other useful information that helps you analyze the health of your cluster.
+
+## Example
+
+```json
+GET _cat/health?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/health?v
+```
+
+## URL parameters
+
+All cat health URL parameters are optional.
+
+Parameter | Type | Description
+:--- | :--- | :---
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+ts | Boolean | If true, returns HH:MM:SS and Unix epoch timestamps. Default is true.
+
+## Response
+
+```json
+GET _cat/health?v&time=5d
+
+epoch | timestamp | cluster | status | node.total | node.data | shards | pri | relo | init | unassign | pending_tasks | max_task_wait_time | active_shards_percent
+1624248112 | 04:01:52 | odfe-cluster | green | 2 | 2 | 16 | 8 | 0 | 0 | 0 | 0 | - | 100.0%
+```

_opensearch/rest-api/cat/cat-indices.md

@@ -0,0 +1,61 @@
+---
+layout: default
+title: cat indices
+parent: CAT
+grand_parent: REST API reference
+nav_order: 25
+has_children: false
+---
+
+# cat indices
+
+The cat indices operation lists information related to indices⁠—how much disk space they are using, how many shards they have, their health status, and so on.
+
+## Example
+
+```
+GET _cat/indices?v
+```
+
+To limit the information to a specific index, add the index name after your query.
+
+```
+GET _cat/indices/<index>?v
+```
+
+If you want to get information for more than one index, separate the indices with commas:
+
+```json
+GET _cat/aliases/index1,index2,index3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/indices/<index>
+GET _cat/indices
+```
+
+## URL parameters
+
+All cat indices URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+bytes | Byte size | Specify the units for byte size. For example, `7kb` or `6gb`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+health | String | Limit indices based on their health status. Supported values are `green`, `yellow`, and `red`.
+include_unloaded_segments | Boolean | Whether to include information from segments not loaded into memory. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+pri | Boolean | Whether to return information only from the primary shards. Default is false.
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+expand_wildcards | Enum | Expands wildcard expressions to concrete indices. Combine multiple values with commas. Supported values are `all`, `open`, `closed`, `hidden`, and `none`. Default is `open`.
+
+
+## Response
+
+```json
+health | status | index | uuid | pri | rep | docs.count | docs.deleted | store.size | pri.store.size
+green  | open | movies | UZbpfERBQ1-3GSH2bnM3sg | 1 | 1 | 1 | 0 | 7.7kb | 3.8kb
+```

_opensearch/rest-api/cat/cat-master.md

@@ -0,0 +1,42 @@
+---
+layout: default
+title: cat master
+parent: CAT
+grand_parent: REST API reference
+nav_order: 30
+has_children: false
+---
+
+# cat master
+
+The cat master operation lists information that helps identify the elected master node.
+
+## Example
+
+```
+GET _cat/master?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/master
+```
+
+## URL parameters
+
+All cat master URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+
+
+## Response
+
+```json
+id                     |   host     |     ip     |   node
+ZaIkkUd4TEiAihqJGkp5CA | 172.18.0.3 | 172.18.0.3 | odfe-node2
+```

_opensearch/rest-api/cat/cat-nodeattrs.md

@@ -0,0 +1,43 @@
+---
+layout: default
+title: cat nodeattrs
+parent: CAT
+grand_parent: REST API reference
+nav_order: 35
+has_children: false
+---
+
+# cat nodeattrs
+
+The cat nodeattrs operation lists the attributes of custom nodes.
+
+## Example
+
+```
+GET _cat/nodeattrs?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/nodeattrs
+```
+
+## URL parameters
+
+All cat nodeattrs URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+
+
+## Response
+
+```json
+node | host | ip | attr | value
+odfe-node2 | 172.18.0.3 | 172.18.0.3 | testattr | test
+```

_opensearch/rest-api/cat/cat-nodes.md

@@ -0,0 +1,50 @@
+---
+layout: default
+title: cat nodes
+parent: CAT
+grand_parent: REST API reference
+nav_order: 40
+has_children: false
+---
+
+# cat nodes
+
+The cat nodes operation lists node-level information, including node roles and load metrics.
+
+A few important node metrics are `pid`, `name`, `master`, `ip`, `port`, `version`, `build`, `jdk`, along with `disk`, `heap`, `ram`, and `file_desc`.
+
+## Example
+
+```
+GET _cat/nodes?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/nodes
+```
+
+## URL parameters
+
+All cat nodes URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+bytes | Byte size | Specify the units for byte size. For example, `7kb` or `6gb`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+full_id | Boolean | If true, return the full node ID. If false, return the shortened node ID. Defaults to false.
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+include_unloaded_segments | Boolean | Whether to include information from segments not loaded into memory. Default is false.
+
+
+## Response
+
+```json
+ip         | heap.percent | ram.percent | cpu load_1m | load_5m | load_15m | node.role | master | name
+172.18.0.3 |     31       |     97      |       3     |  0.03   |   0.10   |  0.14 dimr |  *    |  odfe-node2
+172.18.0.4 |     45       |     97      |       3     |  0.19   |   0.14   |  0.15 dimr |  -    |  odfe-node1
+```

_opensearch/rest-api/cat/cat-pending-tasks.md

@@ -0,0 +1,44 @@
+---
+layout: default
+title: cat pending tasks
+parent: CAT
+grand_parent: REST API reference
+nav_order: 45
+has_children: false
+---
+
+# cat pending tasks
+
+The cat pending tasks operation lists the progress of all pending tasks, including task priority and time in queue.
+
+## Example
+
+```
+GET _cat/pending_tasks?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/pending_tasks
+```
+
+## URL parameters
+
+All cat nodes URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+
+
+## Response
+
+```json
+insertOrder | timeInQueue | priority | source
+  1786      |    1.8s     |  URGENT  | shard-started
+```

_opensearch/rest-api/cat/cat-plugins.md

@@ -0,0 +1,62 @@
+---
+layout: default
+title: cat plugins
+parent: CAT
+grand_parent: REST API reference
+nav_order: 50
+has_children: false
+---
+
+# cat plugins
+
+The cat plugins operation lists the names, components, and versions of the installed plugins.
+
+## Example
+
+```
+GET _cat/plugins?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/plugins
+```
+
+## URL parameters
+
+All cat plugins URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+
+
+## Response
+
+```json
+name       component                       version
+odfe-node2 opendistro-alerting             1.13.1.0
+odfe-node2 opendistro-anomaly-detection    1.13.0.0
+odfe-node2 opendistro-asynchronous-search  1.13.0.1
+odfe-node2 opendistro-index-management     1.13.2.0
+odfe-node2 opendistro-job-scheduler        1.13.0.0
+odfe-node2 opendistro-knn                  1.13.0.0
+odfe-node2 opendistro-performance-analyzer 1.13.0.0
+odfe-node2 opendistro-reports-scheduler    1.13.0.0
+odfe-node2 opendistro-sql                  1.13.2.0
+odfe-node2 opendistro_security             1.13.1.0
+odfe-node1 opendistro-alerting             1.13.1.0
+odfe-node1 opendistro-anomaly-detection    1.13.0.0
+odfe-node1 opendistro-asynchronous-search  1.13.0.1
+odfe-node1 opendistro-index-management     1.13.2.0
+odfe-node1 opendistro-job-scheduler        1.13.0.0
+odfe-node1 opendistro-knn                  1.13.0.0
+odfe-node1 opendistro-performance-analyzer 1.13.0.0
+odfe-node1 opendistro-reports-scheduler    1.13.0.0
+odfe-node1 opendistro-sql                  1.13.2.0
+odfe-node1 opendistro_security             1.13.1.0
+```

_opensearch/rest-api/cat/cat-recovery.md

@@ -0,0 +1,57 @@
+---
+layout: default
+title: cat recovery
+parent: CAT
+grand_parent: REST API reference
+nav_order: 50
+has_children: false
+---
+
+# cat recovery
+
+The cat recovery operation lists all completed and ongoing index and shard recoveries.
+
+## Example
+
+```
+GET _cat/recovery?v
+```
+
+To see only the recoveries of a specific index, add the index name after your query.
+
+```
+GET _cat/recovery/<index>?v
+```
+
+If you want to get information for more than one index, separate the indices with commas:
+
+```json
+GET _cat/aliases/index1,index2,index3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/recovery
+```
+
+## URL parameters
+
+All cat recovery URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+active_only | Boolean | Whether to only include ongoing shard recoveries. Default is false.
+bytes | Byte size | Specify the units for byte size. For example, `7kb` or `6gb`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+detailed | Boolean | Whether to include detailed information about shard recoveries. Default is false.
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+
+## Response
+
+```json
+index | shard | time | type | stage | source_host | source_node | target_host | target_node | repository | snapshot | files | files_recovered | files_percent | files_total | bytes | bytes_recovered | bytes_percent | bytes_total | translog_ops | translog_ops_recovered | translog_ops_percent
+movies | 0 | 117ms | empty_store | done | n/a | n/a | 172.18.0.4 | odfe-node1 | n/a | n/a | 0 | 0 | 0.0% | 0 | 0 | 0 | 0.0% | 0 | 0 | 0 | 100.0%
+movies | 0 | 382ms | peer | done | 172.18.0.4 | odfe-node1 | 172.18.0.3 | odfe-node2 | n/a | n/a | 1 | 1 |  100.0% | 1 | 208 | 208 | 100.0% | 208 | 1 | 1 | 100.0%
+```

_opensearch/rest-api/cat/cat-repositories.md

@@ -0,0 +1,44 @@
+---
+layout: default
+title: cat repositories
+parent: CAT
+grand_parent: REST API reference
+nav_order: 55
+has_children: false
+---
+
+# cat repositories
+
+The cat repositories operation lists all completed and ongoing index and shard recoveries.
+
+## Example
+
+```
+GET _cat/repositories?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/repositories
+```
+
+## URL parameters
+
+All cat repositories URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameters:
+
+Parameter | Type | Description
+:--- | :--- | :---
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+
+
+## Response
+
+```json
+id    type
+repo1   fs
+repo2   s3
+```

_opensearch/rest-api/cat/cat-segments.md

@@ -0,0 +1,55 @@
+---
+layout: default
+title: cat segments
+parent: CAT
+grand_parent: REST API reference
+nav_order: 55
+has_children: false
+---
+
+# cat segments
+
+The cat segments operation lists Lucene segment-level information for each index.
+
+## Example
+
+```
+GET _cat/segments?v
+```
+
+To see only the information about segments of a specific index, add the index name after your query.
+
+```
+GET _cat/segments/<index>?v
+```
+
+If you want to get information for more than one index, separate the indices with commas:
+
+```
+GET _cat/segments/index1,index2,index3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/segments
+```
+
+## URL parameters
+
+All cat segments URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameter:
+
+Parameter | Type | Description
+:--- | :--- | :---
+bytes | Byte size | Specify the units for byte size. For example, `7kb` or `6gb`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/)..
+
+
+## Response
+
+```json
+index | shard | prirep | ip | segment | generation | docs.count | docs.deleted | size | size.memory | committed | searchable | version | compound
+movies | 0 | p | 172.18.0.4 | _0 | 0 | 1 | 0 | 3.5kb | 1364 | true | true | 8.7.0 | true
+movies | 0 | r | 172.18.0.3 | _0 | 0 | 1 | 0 | 3.5kb | 1364 | true | true | 8.7.0 | true
+```

_opensearch/rest-api/cat/cat-shards.md

@@ -0,0 +1,58 @@
+---
+layout: default
+title: cat shards
+parent: CAT
+grand_parent: REST API reference
+nav_order: 60
+has_children: false
+---
+
+# cat shards
+
+The cat shards operation lists the state of all primary and replica shards and how they are distributed.
+
+## Example
+
+```
+GET _cat/shards?v
+```
+
+To see only the information about shards of a specific index, add the index name after your query.
+
+```
+GET _cat/shards/<index>?v
+```
+
+If you want to get information for more than one index, separate the indices with commas:
+
+```
+GET _cat/shards/index1,index2,index3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/shards
+```
+
+## URL parameters
+
+All cat shards URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameter:
+
+Parameter | Type | Description
+:--- | :--- | :---
+bytes | Byte size | Specify the units for byte size. For example, `7kb` or `6gb`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+
+
+## Response
+
+```json
+index | shard | prirep | state   | docs | store | ip |       | node
+plugins | 0   |   p    | STARTED |   0  |  208b | 172.18.0.4 | odfe-node1
+plugins | 0   |   r    | STARTED |   0  |  208b | 172.18.0.3 |  odfe-node2          
+```

_opensearch/rest-api/cat/cat-snapshots.md

@@ -0,0 +1,44 @@
+---
+layout: default
+title: cat snapshots
+parent: CAT
+grand_parent: REST API reference
+nav_order: 65
+has_children: false
+---
+
+# cat snapshots
+
+The cat snapshots operation lists all snapshots for a repository.
+
+## Example
+
+```
+GET _cat/snapshots?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/snapshots
+```
+
+## URL parameters
+
+All cat snapshots URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameter:
+
+Parameter | Type | Description
+:--- | :--- | :---
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+
+
+## Response
+
+```json
+index | shard | prirep | state   | docs | store | ip |       | node
+plugins | 0   |   p    | STARTED |   0  |  208b | 172.18.0.4 | odfe-node1
+plugins | 0   |   r    | STARTED |   0  |  208b | 172.18.0.3 |  odfe-node2          
+```

_opensearch/rest-api/cat/cat-tasks.md

@@ -0,0 +1,45 @@
+---
+layout: default
+title: cat tasks
+parent: CAT
+grand_parent: REST API reference
+nav_order: 70
+has_children: false
+---
+
+# cat tasks
+
+The cat tasks operation lists the progress of all tasks currently running on your cluster.
+
+## Example
+
+```
+GET _cat/tasks?v
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/tasks
+```
+
+## URL parameters
+
+All cat tasks URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameter:
+
+Parameter | Type | Description
+:--- | :--- | :---
+nodes | List | A comma-separated list of node IDs or names to limit the returned information. Use `_local` to return information from the node you're connecting to, specify the node name to get information from specific nodes, or keep the parameter empty to get information from all nodes.
+detailed | Boolean | Returns detailed task information. (Default: false)
+parent_task_id | String | Returns tasks with a specified parent task ID (node_id:task_number). Keep empty or set to -1 to return all.
+time | Time | Specify the units for time. For example, `5d` or `7h`. For more information, see [Supported units]({{site.url}}{{site.baseurl}}/opensearch/units/).
+
+
+## Response
+
+```json
+action | task_id | parent_task_id | type | start_time | timestamp | running_time | ip | node
+cluster:monitor/tasks/lists | 1vo54NuxSxOrbPEYdkSF0w:168062 | - | transport | 1624337809471 | 04:56:49 | 489.5ms | 172.18.0.4 | odfe-node1     
+```

_opensearch/rest-api/cat/cat-templates.md

@@ -0,0 +1,51 @@
+---
+layout: default
+title: cat templates
+parent: CAT
+grand_parent: REST API reference
+nav_order: 70
+has_children: false
+---
+
+# cat templates
+
+The cat templates operation lists the names, patterns, order numbers, and version numbers of index templates.
+
+## Example
+
+```
+GET _cat/templates?v
+```
+
+If you want to get information for more than one template, separate the template names with commas:
+
+```
+GET _cat/shards/template_name_1,template_name_2,template_name_3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/templates
+```
+
+## URL parameters
+
+All cat templates URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameter:
+
+Parameter | Type | Description
+:--- | :--- | :---
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+
+
+## Response
+
+```
+name | index_patterns order version composed_of
+tenant_template | [kibana*] | 0  |    
+```
+
+To learn more about index templates, see [Index templates]({{site.url}}{{site.baseurl}}/opensearch/index-templates).

_opensearch/rest-api/cat/cat-thread-pool.md

@@ -0,0 +1,51 @@
+---
+layout: default
+title: cat thread pool
+parent: CAT
+grand_parent: REST API reference
+nav_order: 75
+has_children: false
+---
+
+# cat thread pool
+
+The cat thread pool operation lists the active, queued, and rejected threads of different thread pools on each node.
+
+## Example
+
+```
+GET _cat/thread_pool?v
+```
+
+If you want to get information for more than one thread pool, separate the thread pool names with commas:
+
+```
+GET _cat/v/thread_pool_name_1,thread_pool_name_2,thread_pool_name_3
+```
+
+## Path and HTTP methods
+
+```
+GET _cat/thread_pool
+```
+
+## URL parameters
+
+All cat thread pool URL parameters are optional.
+
+In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/opensearch/rest-api/cat/index#common-url-parameters), you can specify the following parameter:
+
+Parameter | Type | Description
+:--- | :--- | :---
+local | Boolean | Whether to return information from the local node only instead of from the master node. Default is false.
+master_timeout | Time | The amount of time to wait for a connection to the master node. Default is 30 seconds.
+
+
+## Response
+
+```json
+node_name  name                      active queue rejected
+odfe-node2 ad-batch-task-threadpool    0     0        0
+odfe-node2 ad-threadpool               0     0        0
+odfe-node2 analyze                     0     0        0s 
+```

_opensearch/rest-api/cat/index.md

@@ -0,0 +1,58 @@
+---
+layout: default
+title: CAT
+parent: REST API reference
+nav_order: 100
+has_children: true
+redirect_from:
+  - /opensearch/catapis/
+---
+
+# cat API
+
+You can get essential statistics about your cluster in an easy-to-understand, tabular format using the compact and aligned text (CAT) API. The cat API is a human-readable interface that returns plain text instead of traditional JSON.
+
+Using the cat API, you can answer questions like which node is the elected master, what state is the cluster in, how many documents are in each index, and so on.
+
+## Example
+
+To see the available operations in the cat API, use the following command:
+
+```
+GET _cat
+```
+
+## Common URL parameters
+
+You can use the following string parameters with your query.
+
+Parameter | Description
+:--- | :--- |
+`?v` |  Makes the output more verbose by adding headers to the columns. It also adds some formatting to help align each of the columns together. All examples in this section include the `v` parameter.
+`?help` | Lists the default and other available headers for a given operation.
+`?h`  |  Limits the output to specific headers.
+`?format` |  Outputs the result in JSON, YAML, or CBOR formats.
+`?sort` | Sorts the output by the specified columns.
+
+To see what each column represents, use the `?v` parameter:
+
+```
+GET _cat/<operation_name>?v
+```
+
+To see all the available headers, use the `?help` parameter:
+
+```
+GET _cat/<operation_name>?help
+```
+
+To limit the output to a subset of headers, use the `?h` parameter:
+
+```
+GET _cat/<operation_name>?h=<header_name_1>,<header_name_2>&v
+```
+
+Typically, for any operation you can find out what headers are available using the `?help` parameter, and then use the `?h` parameter to limit the output to only the headers that you care about.
+
+If you use the security plugin, make sure you have the appropriate permissions.
+{: .note }

_opensearch/rest-api/cluster-allocation.md

@@ -0,0 +1,144 @@
+---
+layout: default
+title: Cluster allocation explain
+parent: REST API reference
+nav_order: 10
+---
+
+# Cluster allocation explain
+
+The most basic cluster allocation explain request finds an unassigned shard and explains why it can't be allocated to a node.
+
+If you add some options, you can instead get information on a specific shard, including why OpenSearch assigned it to its current node.
+
+
+## Example
+
+```json
+GET _cluster/allocation/explain?include_yes_decisions=true
+{
+  "index": "movies",
+  "shard": 0,
+  "primary": true
+}
+```
+
+
+## Path and HTTP methods
+
+```
+GET _cluster/allocation/explain
+POST _cluster/allocation/explain
+```
+
+
+## URL parameters
+
+All cluster allocation explain parameters are optional.
+
+Parameter | Type | Description
+:--- | :--- | :---
+include_yes_decisions | Boolean | OpenSearch makes a series of yes or no decisions when trying to allocate a shard to a node. If this parameter is true, OpenSearch includes the (generally more numerous) "yes" decisions in its response. Default is false.
+include_disk_info | Boolean | Whether to include information about disk usage in the response. Default is false.
+
+
+## Request body
+
+All cluster allocation explain fields are optional.
+
+Field | Type | Description
+:--- | :--- | :---
+current_node | String | If you only want an explanation if the shard happens to be on a particular node, specify that node name here.
+index | String | The name of the shard's index.
+primary | Boolean | Whether to provide an explanation for the primary shard (true) or its first replica (false), which share the same shard ID.
+shard | Integer | The shard ID that you want an explanation for.
+
+
+## Response
+
+```json
+{
+  "index": "movies",
+  "shard": 0,
+  "primary": true,
+  "current_state": "started",
+  "current_node": {
+    "id": "d8jRZcW1QmCBeVFlgOJx5A",
+    "name": "opensearch-node1",
+    "transport_address": "172.24.0.4:9300",
+    "weight_ranking": 1
+  },
+  "can_remain_on_current_node": "yes",
+  "can_rebalance_cluster": "yes",
+  "can_rebalance_to_other_node": "no",
+  "rebalance_explanation": "cannot rebalance as no target node exists that can both allocate this shard and improve the cluster balance",
+  "node_allocation_decisions": [{
+    "node_id": "vRxi4uPcRt2BtHlFoyCyTQ",
+    "node_name": "opensearch-node2",
+    "transport_address": "172.24.0.3:9300",
+    "node_decision": "no",
+    "weight_ranking": 1,
+    "deciders": [{
+        "decider": "max_retry",
+        "decision": "YES",
+        "explanation": "shard has no previous failures"
+      },
+      {
+        "decider": "replica_after_primary_active",
+        "decision": "YES",
+        "explanation": "shard is primary and can be allocated"
+      },
+      {
+        "decider": "enable",
+        "decision": "YES",
+        "explanation": "all allocations are allowed"
+      },
+      {
+        "decider": "node_version",
+        "decision": "YES",
+        "explanation": "can relocate primary shard from a node with version [1.0.0] to a node with equal-or-newer version [1.0.0]"
+      },
+      {
+        "decider": "snapshot_in_progress",
+        "decision": "YES",
+        "explanation": "no snapshots are currently running"
+      },
+      {
+        "decider": "restore_in_progress",
+        "decision": "YES",
+        "explanation": "ignored as shard is not being recovered from a snapshot"
+      },
+      {
+        "decider": "filter",
+        "decision": "YES",
+        "explanation": "node passes include/exclude/require filters"
+      },
+      {
+        "decider": "same_shard",
+        "decision": "NO",
+        "explanation": "a copy of this shard is already allocated to this node [[movies][0], node[vRxi4uPcRt2BtHlFoyCyTQ], [R], s[STARTED], a[id=x8w7QxWdQQa188HKGn0iMQ]]"
+      },
+      {
+        "decider": "disk_threshold",
+        "decision": "YES",
+        "explanation": "enough disk for shard on node, free: [35.9gb], shard size: [15.1kb], free after allocating shard: [35.9gb]"
+      },
+      {
+        "decider": "throttling",
+        "decision": "YES",
+        "explanation": "below shard recovery limit of outgoing: [0 < 2] incoming: [0 < 2]"
+      },
+      {
+        "decider": "shards_limit",
+        "decision": "YES",
+        "explanation": "total shard limits are disabled: [index: -1, cluster: -1] <= 0"
+      },
+      {
+        "decider": "awareness",
+        "decision": "YES",
+        "explanation": "allocation awareness is not enabled, set cluster setting [cluster.routing.allocation.awareness.attributes] to enable it"
+      }
+    ]
+  }]
+}
+```