Merge branch 'main' into replace-subs-versions

Author: theletterf

.github/workflows/jekyll.yml

@@ -34,7 +34,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v4
       - name: Setup Ruby
-        uses: ruby/setup-ruby@472790540115ce5bd69d399a020189a8c87d641f # v1.247.0
+        uses: ruby/setup-ruby@bb6434c747fa7022e12fa1cae2a0951fcffcff26 # v1.253.0
         with:
           ruby-version: '3.4.1' # Not needed with a .ruby-version file
           bundler-cache: true # runs 'bundle install' and caches installed gems automatically

docs/reference/edot-collector/config/default-config-k8s.md

@@ -44,6 +44,12 @@ The [`filelog`] and [`hostmetrics`] receivers are used to gather container logs
 
 Logs and metrics are batched for better performance ([`batch`] processor) and then enriched with meta information using the [`k8sattributes`], [`resourcedetection`] and [`resource`] processors.
 
+:::{note}
+The `from_context: client_metadata` option in the `resource` processor only applies to transport-level metadata. It cannot extract custom application attributes.  
+
+To propagate such values into your telemetry, set them explicitly in your application code using EDOT SDK instrumentation. For more information, refer to [EDOT Collector doesn’t propagate client metadata](docs-content://troubleshoot/ingest/opentelemetry/edot-collector/metadata.md).
+:::
+
 ### Application telemetry through OTLP from OTel SDKs
 
 The Daemonset collectors also receive the application telemetry from OTel SDKs that instrument services and pods running on corresponding Kubernetes nodes.

docs/reference/edot-collector/config/default-config-standalone.md

@@ -53,6 +53,12 @@ The goal of EDOT is to preserve OTel data formats and semantics as much as possi
 
 For logs collection, the default configuration uses the [`filelog`] receiver to read log entries from files.  In addition, the [`resourcedetection`] processor enriches the log entries with metadata about the corresponding host and operating system.
 
+:::{note}
+The `from_context: client_metadata` option in the `resource` processor only applies to transport-level metadata. It cannot extract custom application attributes.  
+
+To propagate such values into your telemetry, set them explicitly in your application code using EDOT SDK instrumentation. For more information, refer to [EDOT Collector doesn’t propagate client metadata](docs-content://troubleshoot/ingest/opentelemetry/edot-collector/metadata.md).
+:::
+
 Data is exported directly to {{es}} using the [`elasticsearch`] exporter in `OTel-native` mode.
 
 #### Application and traces collection pipeline

docs/reference/edot-sdks/index.md

@@ -8,9 +8,28 @@ applies_to:
 products:
   - id: cloud-serverless
   - id: observability
+  - id: edot-sdk
 ---
 
-# EDOT SDKs feature overview
+# EDOT SDKs 
+
+The {{edot}} (EDOT) SDKs are production-ready, customized distributions of [OpenTelemetry](https://opentelemetry.io/) language SDKs, specifically optimized for seamless integration with Elastic Observability. EDOT SDKs provide a comprehensive observability solution that automatically captures distributed traces, metrics, and logs from your applications with minimal configuration.
+
+While maintaining full compatibility with the OpenTelemetry specification, EDOT SDKs provide improvements and bug fixes from Elastic before they become available in upstream OpenTelemetry repositories.
+
+## Supported languages
+
+EDOT SDKs are available for the following programming languages and platforms:
+
+* [.NET](/reference/edot-sdks/dotnet/index.md)
+* [Java](/reference/edot-sdks/java/index.md)
+* [Node.js](/reference/edot-sdks/nodejs/index.md)
+* [PHP](/reference/edot-sdks/php/index.md)
+* [Python](/reference/edot-sdks/python/index.md)
+* [Android](/reference/edot-sdks/android/index.md)
+* [iOS](/reference/edot-sdks/ios/index.md)
+
+## Feature overview
 
 This table provides an overview of the features available in the {{edot}} (EDOT) SDKs across different programming languages.
 
@@ -43,7 +62,7 @@ This table provides an overview of the features available in the {{edot}} (EDOT)
 * ❌ Not available
 % end:edot-features
 
-## Elastic support for EDOT SDKs
+## Support for EDOT SDKs
 
 Elastic provides technical support for EDOT Language SDKs according to Elastic's [Support Policy](https://www.elastic.co/support_policy). EDOT SDKs are meant to be used in combination with the [EDOT Collector](/reference/edot-collector/index.md) or the [{{motlp}}](/reference/motlp.md) to ingest data into Elastic solutions from the EDOT SDKs. Other ingestion paths are not officially supported by Elastic.