Merge branch 'main' into 3986-serverless-rns-followup-elasticsearch

Author: theletterf

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,24 @@
+<!--
+Thank you for contributing to the Elastic Docs! 🎉
+Use this template to help us efficiently review your contribution.
+-->
+
+## Summary
+<!--
+Describe what your PR changes or improves.  
+If your PR fixes an issue, link it here. If your PR does not fix an issue, describe the reason you are making the change. 
+-->
+
+## Generative AI disclosure
+<!--
+To help us ensure compliance with the Elastic open source and documentation guidelines, please answer the following:
+-->
+1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
+- [ ] Yes  
+- [ ] No  
+<!--
+2. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).
+
+Tool(s) and model(s) used:
+-->
+

.github/workflows/vale-linting.yml

@@ -0,0 +1,22 @@
+name: Vale Documentation Linting
+
+on:
+  pull_request:
+    paths:
+      - '**.md'
+      - '**.adoc'
+
+permissions:
+  contents: read
+
+jobs:
+  vale:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+      
+      - name: Run Vale Linter
+        uses: elastic/vale-rules/lint@main

.github/workflows/vale-reporting.yml

@@ -0,0 +1,23 @@
+name: Vale Report
+
+on:
+  workflow_run:
+    workflows: ["Vale Documentation Linting"]
+    types:
+      - completed
+
+permissions:
+  pull-requests: read
+
+jobs:
+  report:
+    runs-on: ubuntu-latest
+    if: github.event.workflow_run.event == 'pull_request'
+    permissions:
+      pull-requests: write
+    
+    steps:
+      - name: Post Vale Results
+        uses: elastic/vale-rules/report@main
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -12,4 +12,7 @@ AGENTS.md
 .github/instructions/**.instructions.md
 CLAUDE.md
 GEMINI.md
-.cursor
+.cursor
+
+# VS code settings
+.vscode

contribute-docs/api-docs/kibana-api-docs-quickstart.md

@@ -202,7 +202,7 @@ responses:
 :sync: code-generated
 
 :::{note}
-**This step is optional.** CI will automatically capture the snapshot when you push your `.ts` changes. Running this locally is useful for validating changes before pushing or debugging issues. See [`capture_oas_snapshot.sh`](https://github.com/elastic/kibana/blob/main/.buildkite/scripts/steps/checks/capture_oas_snapshot.sh) for the full list of paths captured in CI.
+**This step is optional.** CI will automatically capture the snapshot when you push your `.ts` changes. Running this locally is useful for validating changes before pushing or debugging issues.
 :::
 
 This step captures the OpenAPI specification that {{kib}} generates at runtime from your route definitions. It spins up a local {{es}} and {{kib}} cluster with your code changes. This generates the following output files in the `oas_docs` directory:
@@ -214,13 +214,27 @@ This step captures the OpenAPI specification that {{kib}} generates at runtime f
 - [Docker](https://docs.docker.com/get-docker/) must be running
 - If you're an Elastician, ensure you're logged into Docker with your Elastic account
 
-**Capture all API paths** (recommended):
+To capture all the documented API paths, copy the command from [`capture_oas_snapshot.sh`](https://github.com/elastic/kibana/blob/main/.buildkite/scripts/steps/checks/capture_oas_snapshot.sh). For example:
 
 ```bash
-node scripts/capture_oas_snapshot --update
+node scripts/capture_oas_snapshot \
+  --include-path /api/status \
+  --include-path /api/alerting/rule/ \
+  --include-path /api/alerting/rules \
+  --include-path /api/actions \
+  --include-path /api/security/role \
+  --include-path /api/spaces \
+  --include-path /api/streams \
+  --include-path /api/fleet \
+  --include-path /api/saved_objects/_import \
+  --include-path /api/saved_objects/_export \
+  --include-path /api/maintenance_window \
+  --include-path /api/agent_builder
+  --update
 ```
 
-**For faster iteration**, capture the specific paths you're working on:
+For faster iteration, you can capture the specific paths you're working on, though this minimized output should not be included in your pull request.
+For example:
 
 ```bash
 node scripts/capture_oas_snapshot --update --include-path /api/your/specific/path

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

@@ -77,7 +77,7 @@ ECK is compatible with the following Kubernetes distributions and related techno
 
 :::{tab-item} ECK 3.2
 * Kubernetes 1.30-1.34
-* OpenShift 4.15-4.19
+* OpenShift 4.15-4.20
 * Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS)
 * Helm: {{eck_helm_minimum_version}}+
 :::

deploy-manage/deploy/deployment-comparison.md

@@ -18,7 +18,7 @@ For more details about feature availability in Serverless, check [](elastic-clou
 
 | Feature/capability | Self-managed | {{ech}} | Serverless |
 |-------------------|-------------|--------------------------------|-------------------------|
-| Hosting | Any infrastructure | {{ecloud}} through AWS, Azure, or GCP | {{ecloud}} through AWS or Azure |
+| Hosting | Any infrastructure | {{ecloud}} through AWS, Azure, or GCP | {{ecloud}} through AWS, Azure, or GCP |
 | Hardware configuration | Full control | Limited control | Managed by Elastic |
 | Autoscaling | No | Available | Automatic |
 | Data tiers management | Through ILM policies | Available | No data tiers |

deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md

@@ -16,8 +16,9 @@ products:
 
 To complete this tutorial, you need:
 
-* The `manage` cluster privilege on the local cluster.
-* A license on both clusters that includes {{ccr}}. [Activate a free 30-day trial](../../license/manage-your-license-in-self-managed-cluster.md).
-* An index on the remote cluster that contains the data you want to replicate. This tutorial uses the sample eCommerce orders data set. [Load sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana).
-* In the local cluster, all nodes with the `master` [node role](elasticsearch://reference/elasticsearch/configuration-reference/node-settings.md#node-roles) must also have the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. The local cluster must also have at least one node with both a data role and the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. Individual tasks for coordinating replication scale based on the number of data nodes with the `remote_cluster_client` role in the local cluster.
+- The `manage` cluster privilege on the local cluster.
+- Both clusters must have the same [license](/deploy-manage/license.md) type, and that license must support {{ccr}}.
+  - [Activate a free 30-day trial](../../license/manage-your-license-in-self-managed-cluster.md).
+- An index on the remote cluster that contains the data you want to replicate. This tutorial uses the sample eCommerce orders data set. [Load sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana).
+- In the local cluster, all nodes with the `master` [node role](elasticsearch://reference/elasticsearch/configuration-reference/node-settings.md#node-roles) must also have the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. The local cluster must also have at least one node with both a data role and the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. Individual tasks for coordinating replication scale based on the number of data nodes with the `remote_cluster_client` role in the local cluster.
 

explore-analyze/_snippets/lens-breakdown-advanced-settings.md

@@ -0,0 +1,9 @@
+:::{dropdown} Advanced settings
+Several advanced options allow you to refine the behavior of the breakdown:
+
+- **Include documents without the selected field**: Off by default.
+- **Group remaining values as "Other"**: On by default.
+- **Enable accuracy mode**: This option improves results for high-cardinality data, but increases the load on the {{es}} cluster.
+- **Include values**: Values from the breakdown dimension to always show a tile for.
+- **Exclude values**: Values from the breakdown dimension to always exclude from the displayed tiles.
+:::

explore-analyze/_snippets/lens-value-advanced-settings.md

@@ -0,0 +1,9 @@
+:::{dropdown} Advanced settings
+Depending on the data you defined, several options allow you to apply additional filtering to the data taken into account to compute the metric's value:
+    
+- **Normalize by unit**: Normalize the metric values to show per unit of time.
+- **Filter by**: Specify a query.
+- **Reduced time range**: Reduce the time range specified on the dashboard's time filter by the specified duration.
+- **Time shift**: Shift the time range by the specified duration. This is useful if the value should use a different time range than the one selected on the dashboard.
+- **Hide zero values**: Don't show values equal to zero. This option is on by default.
+:::