Merge branch 'main' into mw-tsds-downsampling

Author: marciw

.github/workflows/update-kube-stack-version.yml

@@ -0,0 +1,65 @@
+name: Update Kube-Stack Version
+
+on:
+  schedule:
+    # Run every Monday at 9:00 AM UTC
+    - cron: '0 9 * * 1'
+  workflow_dispatch: # Allow manual triggering
+
+jobs:
+  update-kube-stack-version:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+    
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.9'
+    
+    - name: Run kube-stack version update script
+      run: |
+        cd scripts
+        python update_kube_stack_version.py
+    
+    - name: Check for changes
+      id: verify-changed-files
+      run: |
+        if [ -n "$(git status --porcelain)" ]; then
+          echo "changed=true" >> $GITHUB_OUTPUT
+        else
+          echo "changed=false" >> $GITHUB_OUTPUT
+        fi
+    
+    - name: Commit and push changes
+      if: steps.verify-changed-files.outputs.changed == 'true'
+      run: |
+        git config --local user.email "[email protected]"
+        git config --local user.name "GitHub Action"
+        git add docs/docset.yml
+        git commit -m "chore: update kube-stack version [skip ci]"
+        git push
+    
+    - name: Create Pull Request
+      if: steps.verify-changed-files.outputs.changed == 'true'
+      uses: peter-evans/create-pull-request@v5
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        commit-message: "chore: update kube-stack version"
+        title: "chore: update kube-stack version"
+        body: |
+          This PR automatically updates the kube-stack version in `docs/docset.yml` based on the latest version from the elastic-agent repository.
+          
+          **Changes:**
+          - Updated kube-stack version in docset.yml
+          
+          This PR was created automatically by the weekly kube-stack version update workflow.
+        branch: update-kube-stack-version
+        delete-branch: true
+        labels: |
+          automated
+          documentation

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

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration
 ---
 
-# Configuration [k8s-beat-configuration]
+# Configuration for Beats on {{eck}} [k8s-beat-configuration]
 
 ## Upgrade the Beat specification [k8s-beat-upgrade-specification]
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-beats.md

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration examples
 ---
 
-# Configuration Examples [k8s-beat-configuration-examples]
+# Beats configuration examples on {{eck}} [k8s-beat-configuration-examples]
 
 In this section you can find manifests that address a number of common use cases and can be your starting point in exploring Beats deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured Kubernetes cluster. They all contain three-node {{es}} cluster and single {{kib}} instance. All Beat configurations set up {{kib}} dashboards if they are available for a given Beat and all required RBAC resources.
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-fleet.md

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration examples
 ---
 
-# Configuration Examples [k8s-elastic-agent-fleet-configuration-examples]
+# Fleet managed agents configuration examples on {{eck}} [k8s-elastic-agent-fleet-configuration-examples]
 
 This section contains manifests that illustrate common use cases, and can be your starting point in exploring {{agent}} deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured {{k8s}} cluster. They all contain a three-node {{es}} cluster, a single {{kib}} instance and a single {{fleet-server}} instance.
 

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

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration examples
 ---
 
-# Configuration examples [k8s-logstash-configuration-examples]
+# Logstash configuration examples on {{eck}} [k8s-logstash-configuration-examples]
 
 This section contains manifests that illustrate common use cases, and can be your starting point in exploring Logstash deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured Kubernetes cluster. They all contain a three-node {{es}} cluster and a single {{kib}} instance.
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-standalone.md

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration examples
 ---
 
-# Configuration examples [k8s-elastic-agent-configuration-examples]
+# Standalone Elastic Agent configuration examples on {{eck}} [k8s-elastic-agent-configuration-examples]
 
 This section contains manifests that illustrate common use cases, and can be your starting point in exploring Elastic Agent deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured Kubernetes cluster. They all contain a three-node {{es}} cluster and a single {{kib}} instance. Add the corresponding integration package to {{kib}} to install the dashboards, visualizations and other assets for each of these examples as described in [the Elastic Agent documentation](/reference/fleet/install-elastic-agents.md).
 

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

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration
 ---
 
-# Configuration [k8s-elastic-agent-fleet-configuration]
+# Configuration for Fleet managed agents on {{eck}} [k8s-elastic-agent-fleet-configuration]
 
 {{fleet}}-managed {{agents}} must connect to {{fleet-server}} to receive their configurations. You can deploy {{fleet-server}} instances using ECKs Agent CRD with the appropriate configuration, as shown in [Fleet mode and Fleet Server](#k8s-elastic-agent-fleet-configuration-fleet-mode-and-fleet-server).
 

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

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration
 ---
 
-# Configuration [k8s-logstash-configuration]
+# Configuration for Logstash on {{eck}} [k8s-logstash-configuration]
 
 ## Upgrade the Logstash specification [k8s-logstash-upgrade-specification]
 

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

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration
 ---
 
-# Configuration [k8s-elastic-agent-configuration]
+# Configuration for standalone Elastic Agents on {{eck}} [k8s-elastic-agent-configuration]
 
 ## Upgrade the Elastic Agent specification [k8s-elastic-agent-upgrade-specification]
 

deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md

@@ -111,7 +111,7 @@ This table compares Observability capabilities between {{ech}} deployments and O
 | **APM integration** | ✅ | ✅ | Use **Managed Intake Service** (supports Elastic APM and OTLP protocols) <br> Refer to [Managed OTLP endpoint](opentelemetry://reference/motlp.md) for OTLP data ingestion |
 | [**APM Agent Central Configuration**](/solutions/observability/apm/apm-agent-central-configuration.md) | ✅ | ❌ | Not available in Serverless |
 | [**APM Tail-based sampling**](/solutions/observability/apm/transaction-sampling.md#apm-tail-based-sampling) | ✅ | ❌ | - Not available in Serverless <br>- Consider **OpenTelemetry** tail sampling processor as an alternative |
-| [**Android agent/SDK instrumentation**](opentelemetry://reference/edot-sdks/android/index.md) | ✅ | ✅ | |
+| [**Android agent/SDK instrumentation**](apm-agent-android://reference/edot-android/index.md) | ✅ | ✅ | |
 | [**AWS Firehose integration**](/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md) | ✅ | ✅ | |
 | [**Custom roles for Kibana Spaces**](/deploy-manage/manage-spaces.md#spaces-control-user-access) | ✅ | ✅ | |
 | [**Data stream lifecycle**](/manage-data/lifecycle/data-stream.md) | ✅ | ✅ | Primary lifecycle management method in Serverless |
@@ -121,7 +121,7 @@ This table compares Observability capabilities between {{ech}} deployments and O
 | **[Fleet Agent policies](/reference/fleet/agent-policy.md)** | ✅ | ✅ | |
 | **[Fleet server](/reference/fleet/fleet-server.md)** | - Self-hosted <br>- Hosted | ✅ | Fully managed by Elastic |
 | [**Index lifecycle management**](/manage-data/lifecycle/index-lifecycle-management.md) | ✅ | ❌ | Use [**Data stream lifecycle**](/manage-data/lifecycle/data-stream.md) instead |
-| **[iOS agent/SDK instrumentation](opentelemetry://reference/edot-sdks/ios/index.md)** | ✅ | ✅ | |
+| **[iOS agent/SDK instrumentation](apm-agent-ios://reference/edot-ios/index.md)** | ✅ | ✅ | |
 | **[Kibana Alerts](/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md)** | ✅ | ✅ | |
 | **[LogsDB index mode](/manage-data/data-store/data-streams/logs-data-stream.md)** | ✅ | ✅ | - Reduces storage footprint <br> - Enabled by default <br>- Cannot be disabled |
 | **[Logs management](/solutions/observability/logs.md)** | ✅ | ✅ | |