Merge branch 'main' into frconil-patch-2

Author: eedugon

.github/CODEOWNERS

@@ -1,5 +1,66 @@
-/.github/ @elastic/doc-leads
-/.github/workflows/ @elastic/docs-engineering
+# Unless a later match takes precedence, someone on the docs team must review all PRs to this repo
+*                                           @elastic/docs
 
-/serverless/ @elastic/platform-docs
-/serverless/serverless-changelog.asciidoc @elastic/docs
+# Templates, workflows, and config
+/.github/                                   @elastic/doc-leads
+/.github/workflows/                         @elastic/docs-engineering
+/acrolinx/                                  @elastic/doc-leads
+
+# The docs
+/cloud-account/                             @elastic/admin-docs
+/deploy-manage/                             @elastic/admin-docs
+/explore-analyze/                           @elastic/core-docs @elastic/experience-docs 
+/extend/                                    @elastic/core-docs
+/get-started/                               @elastic/core-docs
+
+/manage-data/                               @elastic/admin-docs
+/manage-data/data-store/                    @elastic/admin-docs @elastic/developer-docs 
+/manage-data/ingest/                        @elastic/ingest-docs
+
+/reference/                                 @elastic/docs
+/reference/apm-agents/                      @elastic/ingest-docs
+/reference/data-analysis/                   @elastic/docs
+/reference/data-analysis/observability/     @elastic/experience-docs
+/reference/data-analysis/kibana/            @elastic/experience-docs 
+/reference/data-analysis/machine-learning/  @elastic/developer-docs
+/reference/data-analysis/observability/     @elastic/experience-docs
+/reference/elasticsearch/clients/           @elastic/developer-docs
+/reference/fleet/                           @elastic/ingest-docs
+/reference/glossary/                        @elastic/docs
+/reference/ingestion-tools/                 @elastic/ingest-docs
+/reference/observability/                   @elastic/experience-docs
+/reference/search/                          @elastic/developer-docs
+/reference/security/                        @elastic/experience-docs
+
+/release-notes/                             @elastic/docs
+
+/release-notes/apm-agents/                  @elastic/ingest-docs
+/release-notes/elastic-cloud-serverless/    @elastic/admin-docs
+/release-notes/elastic-observability/       @elastic/ski-docs
+/release-notes/elastic-security/            @elastic/ski-docs
+/release-notes/elasticsearch-clients/       @elastic/developer-docs
+/release-notes/fleet-elastic-agent/         @elastic/ingest-docs
+/release-notes/intro/                       @elastic/docs
+
+/solutions/                                 @elastic/experience-docs @elastic/developer-docs 
+/solutions/observability/                   @elastic/experience-docs
+/solutions/observability/get-started/       @elastic/ski-docs
+/solutions/search/                          @elastic/developer-docs
+/solutions/security/                        @elastic/experience-docs
+/solutions/security/cloud/                  @elastic/ingest-docs
+
+/troubleshoot/                              @elastic/docs
+/troubleshoot/deployments/                  @elastic/admin-docs
+/troubleshoot/elasticsearch/                @elastic/admin-docs
+/troubleshoot/ingest/                       @elastic/ingest-docs
+/troubleshoot/kibana/                       @elastic/admin-docs @elastic/experience-docs 
+/troubleshoot/monitoring/                   @elastic/admin-docs @elastic/experience-docs
+/troubleshoot/observability/                @elastic/ski-docs
+/troubleshoot/security/                     @elastic/ski-docs
+
+# Raw migrated files
+/raw-migrated-files/                        @elastic/docs
+
+# Legacy serverless docs
+/serverless/                                @elastic/admin-docs
+/serverless/serverless-changelog.asciidoc   @elastic/docs

.github/ISSUE_TEMPLATE/community-request.yaml renamed to .github/ISSUE_TEMPLATE/a-community-request.yaml

@@ -1,14 +1,14 @@
 name: "Community documentation request"
-description: Request a documentation change or enhancement.
-title: "[Request]: "
-labels: ["Request", "community"]
+description: An issue template for non-Elastic employees to request changes to the documentation.
+title: "[Community]: "
+labels: ["community"]
 body:
   - type: markdown
     attributes:
       value: |
-        Hi 👋. Thanks for taking the time to fill out this request!
-        This form will create an issue that Elastic's docs team will triage and prioritize.
-        You can also open a PR instead.
+        This issue template is for non-Elastic employees to request changes to the documentation. **If you are an Elastic employee, please use the internal issue template instead.**
+        
+        This form will create an issue that Elastic's docs team will triage and prioritize. You can also open a PR instead. Thanks for taking the time to fill out this request!
   - type: textarea
     id: link
     attributes:

.github/ISSUE_TEMPLATE/internal-request.yaml renamed to .github/ISSUE_TEMPLATE/b-internal-request.yaml

@@ -1,7 +1,6 @@
 name: "Internal documentation request (Elastic employees)"
-description: Request a documentation change or enhancement for any supported release.
-title: "[REQUEST]: "
-labels: ["request", "Team:Docs"]
+description: An issue template for Elastic employees to request improvements, additions, or changes to the documentation.
+title: "[Internal]: "
 body:
   - type: markdown
     attributes:
@@ -69,6 +68,14 @@ body:
       default: 0
     validations:
       required: true
+  - type: input
+    id: release-serverless
+    attributes:
+      label: Serverless release
+      description: When do you expect the feature to be promoted and available in the _**serverless production environment**_?
+      placeholder: The week of April 1, 2024
+    validations:
+      required: true    
   - type: dropdown
     id: collaboration
     attributes:

.github/ISSUE_TEMPLATE/api-feedback.yaml renamed to .github/ISSUE_TEMPLATE/c-api-feedback.yaml

@@ -1,7 +1,7 @@
 name: "API docs feedback"
 description: Tell us about your experience with Elastic API documentation.
-title: "[Feedback]: "
-labels: ["feedback", "community"]
+title: "[API]: "
+labels: ["api-feedback"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/ui-copy-request.yaml renamed to .github/ISSUE_TEMPLATE/d-ui-copy-request.yaml

@@ -1,14 +1,12 @@
-name: "Docs issue"
-description: Report documentation issues such as inaccuracies, broken links, typos, or missing information.
-title: "[Issue]: "
-labels: ["triage"]
+name: "Website issue"
+description: This issue template should only be used when navigating directly from elastic.co.
+title: "[Website]: "
+labels: ["source:web"]
 body:
   - type: markdown
     attributes:
       value: |
-        Hi 👋. Thanks for taking the time to fill out this issue report!
-        This form will create an issue that Elastic's docs team will triage and prioritize.
-        You can also open a PR instead.
+        Hi 👋. Thanks for taking the time to fill out this issue report! This form will create an issue that Elastic's docs team will triage and prioritize. You can also open a PR instead.
   - type: dropdown
     attributes:
       label: Type of issue

.github/ISSUE_TEMPLATE/issue-report.yaml

@@ -12,6 +12,10 @@ jobs:
   route:
     runs-on: ubuntu-latest
     if: |
+      github.event.label.name == 'team:Ingest' ||
+      github.event.label.name == 'team:Experience' ||
+      github.event.label.name == 'team:Admin' ||
+      github.event.label.name == 'team:Developer' ||
       github.event.label.name == 'team:DocsEng' ||
       github.event.label.name == 'team:Obs' ||
       github.event.label.name == 'team:Platform' ||
@@ -21,12 +25,16 @@ jobs:
     env:
       PROJECT_ID_MAP: |
         {
-          "team:DocsEng":   "1625",
-          "team:Obs":       "649",
-          "team:Platform":  "1232",
-          "team:Projects":  "1415",
-          "team:Search":    "726",
-          "team:Security":  "1034"
+          "team:Ingest":      "649",
+          "team:Experience":  "1034",
+          "team:Admin":       "1927",
+          "team:Developer":   "726",
+          "team:DocsEng":     "1625",
+          "team:Obs":         "649",
+          "team:Platform":    "1232",
+          "team:Projects":    "1415",
+          "team:Search":      "726",
+          "team:Security":    "1034"
         }
     steps:
       - name: Remove needs-team label

.github/workflows/add-to-board.yml

@@ -60,7 +60,7 @@ To enable multifactor authentication using an authenticator app, you must verify
 
 You can remove a multifactor authentication method after it’s added by clicking **Remove**.
 
-Before you remove an authentication method, you must set up an alternate method. If you can’t use any of your configured authentication methods — for example, if your device is lost or stolen — then [contact support](../troubleshoot/index.md).
+Before you remove an authentication method, you must set up an alternate method. If you can’t use any of your configured authentication methods — for example, if your device is lost or stolen — then [contact support](../troubleshoot/index.md).
 
 
 ## Frequently asked questions [ec-account-security-mfa-faq]

cloud-account/multifactor-authentication.md

@@ -71,7 +71,7 @@ For a data tier, an autoscaling event can be triggered in the following cases:
 
 * Through ILM  policies. For example, if a deployment has only hot nodes and autoscaling is enabled, it automatically creates warm or cold nodes, if an ILM policy is trying to move data from hot to warm or cold nodes.
 
-On machine learning nodes, scaling is determined by an estimate of the memory and CPU requirements for the currently configured jobs and trained models. When a new machine learning job tries to start, it looks for a node with adequate native memory and CPU capacity. If one cannot be found, it stays in an `opening` state. If this waiting job exceeds the queueing limit set in the machine learning decider, a scale up is requested. Conversely, as machine learning jobs run, their memory and CPU usage might decrease or other running jobs might finish or close. In this case, if the duration of decreased resource usage exceeds the set value for `down_scale_delay`, a scale down is requested. Check [Machine learning decider](autoscaling-deciders.md)for more detail. To learn more about machine learning jobs in general, check [Create anomaly detection jobs](../../explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md#ml-ad-create-job)
+On machine learning nodes, scaling is determined by an estimate of the memory and CPU requirements for the currently configured jobs and trained models. When a new machine learning job tries to start, it looks for a node with adequate native memory and CPU capacity. If one cannot be found, it stays in an `opening` state. If this waiting job exceeds the queueing limit set in the machine learning decider, a scale up is requested. Conversely, as machine learning jobs run, their memory and CPU usage might decrease or other running jobs might finish or close. In this case, if the duration of decreased resource usage exceeds the set value for `down_scale_delay`, a scale down is requested. Check [Machine learning decider](autoscaling-deciders.md) for more detail. To learn more about machine learning jobs in general, check [Create anomaly detection jobs](../../explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md#ml-ad-create-job).
 
 On a highly available deployment, autoscaling events are always applied to instances in each availability zone simultaneously, to ensure consistency.
 
@@ -650,4 +650,4 @@ curl -XPOST \
 
 :::
 
-::::
+::::

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

@@ -39,13 +39,13 @@ Data Transfer accounts for the volume of data (payload) going into, out of, and
 
 We meter and bill data transfer using three dimensions:
 
-1. Data in (free)
+1. Data in (free)
 :   *Data in* accounts for all of the traffic going into the deployment. It includes index requests with data payload, as well as queries sent to the deployment (although the byte size of the latter is typically much smaller).
 
-2. Data out
+2. Data out
 :   *Data out* accounts for all of the traffic coming out of the deployment. This includes search results, as well as monitoring data sent from the deployment. The same rate applies regardless of the destination of the data, whether to the internet, to another region, or to a cloud provider account in the same region. Data coming out of the deployment through AWS PrivateLink, GCP Private Service Connect, or Azure Private Link, is also considered *Data out*.
 
-3. Data inter-node
+3. Data inter-node
 :   *Data inter-node* accounts for all of the traffic sent between the components of the deployment. This includes the data sync between nodes of a cluster which is managed automatically by {{es}} cluster sharding. It also includes data related to search queries executed across multiple nodes of a cluster. Note that single-node {{es}} clusters typically have lower charges, but may still incur inter-node charges accounting for data exchanged with {{kib}} nodes or other nodes, such as machine learning or APM.
 
 We provide a free allowance of 100GB per month, which includes the sum of *data out* and *data inter-node*, across all deployments in the account. Once this threshold is passed, a charge is applied for any data transfer used in excess of the 100GB monthly free allowance.
@@ -71,15 +71,15 @@ Storage costs are tied to the cost of storing the backup snapshots in the underl
 
 As is common with Cloud providers, we meter and bill snapshot storage using two dimensions:
 
-1. Storage size (GB/month)
+1. Storage size (GB/month)
 :   This is calculated by metering the storage space (GBs) occupied by all snapshots of all deployments tied to an account. The same unit price applies to all regions. To calculate the due charges, we meter the amount of storage on an hourly basis and produce an average size (in GB) for a given month. The average amount is then used to bill the account for the GB/month used within a billing cycle (a calendar month).
 
     For example, if the storage used in April 2019 was 100GB for 10 days, and then 130GB for the remaining 20 days of the month, the average storage would be 120 GB/month, calculated as (100*10 + 130*20)/30.
 
     We provide a free allowance of 100 GB/month to all accounts across all the account deployments. Any metered storage usage below that amount will not be billed. Whenever the 100 GB/month threshold is crossed, we bill for the storage used in excess of the 100GB/month free allowance.
 
 
-2. Storage API requests (1K Requests/month)
+2. Storage API requests (1K Requests/month)
 :   These costs are calculated by counting the total number of calls to backup or restore snapshots made by all deployments associated with an account. Unlike storage size, this dimension is cumulative, summed up across the billing cycle, and is billed at a price of 1,000 requests.
 
     We provide a free allowance of 100,000 API requests to all accounts each month across all the account deployments. Once this threshold is passed, we bill only for the use of API requests in excess of the free allowance.

deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md

@@ -141,7 +141,7 @@ Verify that required traffic is allowed. Check the [Networking prerequisites](ec
         [...]
         ```
 
-6. If podman requires a proxy in your infrastructure setup, modify the `/usr/share/containers/containers.conf` file and add the `HTTP_PROXY` and `HTTPS_PROXY` environment variables in the [engine] section. Note that multiple env variables in that configuration file exists — use the one in the [engine] section.
+6. If podman requires a proxy in your infrastructure setup, modify the `/usr/share/containers/containers.conf` file and add the `HTTP_PROXY` and `HTTPS_PROXY` environment variables in the [engine] section. Note that multiple env variables in that configuration file exists — use the one in the [engine] section.
 
     Example:
 

deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md

@@ -171,7 +171,7 @@ Using Docker or Podman as container runtime is a configuration local to the host
         [...]
         ```
 
-6. If podman requires a proxy in your infrastructure setup, modify the `/usr/share/containers/containers.conf` file and add the `HTTP_PROXY` and `HTTPS_PROXY` environment variables in the [engine] section. Note that multiple env variables in that configuration file exists — use the one in the [engine] section.
+6. If podman requires a proxy in your infrastructure setup, modify the `/usr/share/containers/containers.conf` file and add the `HTTP_PROXY` and `HTTPS_PROXY` environment variables in the [engine] section. Note that multiple env variables in that configuration file exists — use the one in the [engine] section.
 
     Example:
 

deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md

@@ -341,7 +341,7 @@ If the volume driver supports `ExpandInUsePersistentVolumes`, the filesystem is
 
 If the volume driver does not support `ExpandInUsePersistentVolumes`, you must manually delete Pods after the resize so that they can be recreated automatically with the expanded filesystem.
 
-Any other changes in the volumeClaimTemplates—​such as changing the storage class or decreasing the volume size—​are not allowed. To make changes such as these, you must fully delete the {{ls}} resource, delete and recreate or resize the volume, and create a new {{ls}} resource.
+Any other changes in the volumeClaimTemplates—such as changing the storage class or decreasing the volume size—are not allowed. To make changes such as these, you must fully delete the {{ls}} resource, delete and recreate or resize the volume, and create a new {{ls}} resource.
 
 Before you delete a persistent queue (PQ) volume, ensure that the queue is empty. We recommend setting `queue.drain: true` on the {{ls}} Pods to ensure that the queue is drained when Pods are shutdown. Note that you should also increase the `terminationGracePeriodSeconds` to a large enough value to allow the queue to drain.
 

deploy-manage/deploy/cloud-on-k8s/configuration-logstash.md

@@ -93,7 +93,7 @@ data:
     ubi-only: false
 ```
 
-Alternatively, you can edit the `elastic-operator` StatefulSet and add flags to the `args` section of the operator container — which will trigger an automatic restart of the operator pod by the StatefulSet controller.
+Alternatively, you can edit the `elastic-operator` StatefulSet and add flags to the `args` section of the operator container — which will trigger an automatic restart of the operator pod by the StatefulSet controller.
 
 ## Configure ECK under Operator Lifecycle Manager [k8s-operator-config-olm]
 

deploy-manage/deploy/cloud-on-k8s/configure-eck.md

@@ -10,7 +10,7 @@ products:
 
 # Configure the validating webhook [k8s-webhook]
 
-ECK can be configured to provide a [validating webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) that validates Elastic custom resources ({{eck_resources_list}}) before they are created or updated. Validating webhooks provide immediate feedback if a submitted manifest contains invalid or illegal configuration — which can help you catch errors early and save time that would otherwise be spent on troubleshooting.
+ECK can be configured to provide a [validating webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) that validates Elastic custom resources ({{eck_resources_list}}) before they are created or updated. Validating webhooks provide immediate feedback if a submitted manifest contains invalid or illegal configuration — which can help you catch errors early and save time that would otherwise be spent on troubleshooting.
 
 Validating webhooks are defined using a `ValidatingWebhookConfiguration` object that defines the following:
 
@@ -30,7 +30,7 @@ Validating webhooks are defined using a `ValidatingWebhookConfiguration` object
 When using the default `operator.yaml` manifest, ECK is installed with a `ValidatingWebhookConfiguration` configured as follows:
 
 * Validate all known Elastic custom resources ({{eck_resources_list}}) on create and update.
-* The operator itself is the webhook server — which is exposed through a service named `elastic-webhook-server` in the `elastic-system` namespace.
+* The operator itself is the webhook server — which is exposed through a service named `elastic-webhook-server` in the `elastic-system` namespace.
 * The operator generates a certificate for the webhook and stores it in a secret named `elastic-webhook-server-cert` in the `elastic-system` namespace. This certificate is automatically rotated by the operator when it is due to expire.