mOTLP for ECH GA

docs/reference/_snippets/find-motlp-endpoint.md

@@ -9,8 +9,7 @@ To retrieve your {{motlp}} endpoint address and API key, follow these steps:
 Alternatively, you can retrieve the endpoint from the **Manage project** page and create an API key manually from the **API keys** page.
 :::
 
-:::{applies-item} ess: preview
-You need an {{ech}} deployment version 9.2 or later.
+:::{applies-item} ess:
 1. In {{ecloud}}, create an {{ech}} deployment or open an existing one.
 2. Go to **Add data**, select **Applications** and then select **OpenTelemetry**.
 3. Copy the endpoint and authentication headers values.

docs/reference/architecture/hosts_vms.md

@@ -5,6 +5,8 @@ applies_to:
   stack:
   serverless:
     observability:
+  deployment: 
+    ess: 
 products:
   - id: cloud-serverless
   - id: observability
@@ -38,10 +40,10 @@ The following sections outline the recommended architectures for different Elast
 Users can send data direct from the Collectors or SDKs deployed on the edge environment through OTLP without any additional requirements for managing an ingestion layer.
 ::::
 
-::::{applies-item} ess: preview
+::::{applies-item} ess:
 
 :::{note}
-You need an {{ech}} deployment version 9.2 or later.
+You need an {{ech}} deployment version 9.0 or later, or version 8.19 or later.
 :::
 
 {{ech}} provides a [Managed OTLP Endpoint](/reference/motlp.md) for ingestion of OpenTelemetry data. Users can send data direct from the Collectors or SDKs deployed on the edge environment through OTLP without any additional requirements for managing an ingestion layer.
@@ -50,7 +52,7 @@ You need an {{ech}} deployment version 9.2 or later.
 ::::
 
 ::::{applies-item} { eck:, ece:, self: }
-In a self-managed Elastic deployment, we recommend running an EDOT Collector in gateway mode as a unified ingestion layer for OTLP telemetry from OpenTelemetry collectors or SDKs running at the edge. This gateway can receive all signals (logs, metrics and traces), apply processing as needed, and cover the same use cases that previously required components like APM Server or Logstash.
+In a self-managed Elastic deployment, we recommend running an EDOT Collector in gateway mode as a unified ingestion layer for OTLP telemetry from OpenTelemetry collectors or SDKs running at the edge. This gateway can receive all signals (logs, metrics and traces), apply processing as needed, and cover the same use cases that previously required components like {{product.apm-server}} or {{product.logstash}}.
 
 Depending on your scalability and durability needs, this can be a single collector that scales horizontally, or a chain of collectors where each tier handles a specific concern. For high availability and stronger durability guarantees, you can insert Kafka between tiers so that ingestion is buffered and resilient to downstream outages.
 

docs/reference/architecture/k8s.md

@@ -5,6 +5,8 @@ applies_to:
   stack:
   serverless:
     observability:
+  deployment:
+    ess:
 products:
   - id: cloud-serverless
   - id: observability
@@ -67,10 +69,10 @@ The following sections outline the recommended architectures for different Elast
 For a Kubernetes setup, the gateway Collector in your cluster sends OTLP data directly to the Managed OTLP Endpoint. There is no need for an EDOT gateway collector on the backend side. You can optionally deploy an EDOT Collector in gateway mode as part of your edge environment if you need additional processing before data reaches the Managed OTLP Endpoint.
 ::::
 
-::::{applies-item} ess: preview
+::::{applies-item} ess:
 
 :::{note}
-You need an {{ech}} deployment version 9.2 or later.
+You need an {{ech}} deployment version 9.0 or later, or version 8.19 or later.
 :::
 
 {{ech}} provides a [Managed OTLP Endpoint](/reference/motlp.md) for ingestion of OpenTelemetry data.

docs/reference/motlp.md

@@ -2,12 +2,13 @@
 navigation_title: Managed OTLP Endpoint
 description: Reference documentation for the Elastic Cloud Managed OTLP Endpoint.
 applies_to:
-  # Preserve when going GA  
   serverless:
     observability:
     security:
   deployment:
-    ess: preview
+    ess: ga
+    eck: unavailable
+    ece: unavailable
     self: unavailable
 products:
   - id: cloud-serverless
@@ -17,10 +18,12 @@ products:
 
 # Elastic Cloud Managed OTLP Endpoint (mOTLP)
 
-The {{motlp}} allows you to send OpenTelemetry data directly to {{ecloud}} using the OTLP protocol. The endpoint adds a resilient ingestion layer that works seamlessly with serverless autoscaling and removes pressure from {{ech}} clusters.
+The {{motlp}} allows you to send OpenTelemetry data directly to {{ecloud}} using the OTLP protocol. 
+
+The endpoint adds a resilient ingestion layer that works seamlessly with serverless autoscaling and removes pressure from {{ech}} clusters.
 
 :::{important}
-The {{motlp}} endpoint is not available for Elastic [self-managed](docs-content://deploy-manage/deploy/self-managed.md), [ECE](docs-content://deploy-manage/deploy/cloud-enterprise.md) or [ECK](docs-content://deploy-manage/deploy/cloud-on-k8s.md) clusters. To send OTLP data to any of these cluster types, deploy and expose an OTLP-compatible endpoint using the EDOT Collector as a gateway. Refer to [EDOT deployment docs](elastic-agent://reference/edot-collector/modes.md#edot-collector-as-gateway) for more information.
+The {{motlp}} endpoint is not available for Elastic [self-managed](docs-content://deploy-manage/deploy/self-managed.md), [ECE](docs-content://deploy-manage/deploy/cloud-enterprise.md), or [ECK](docs-content://deploy-manage/deploy/cloud-on-k8s.md) clusters. To send OTLP data to any of these cluster types, deploy and expose an OTLP-compatible endpoint using the [EDOT Collector as a gateway](elastic-agent://reference/edot-collector/modes.md#edot-collector-as-gateway).
 :::
 
 ## Reference architecture
@@ -107,7 +110,7 @@ The following limitations apply when using the {{motlp}}:
 * Universal Profiling is not available.
 * Only supports histograms with delta temporality. Cumulative histograms are dropped.
 * Latency distributions based on histogram values have limited precision due to the fixed boundaries of explicit bucket histograms.
-* [Traffic filters](docs-content://deploy-manage/security/ip-filtering-cloud.md) are not yet available on both ECH and Serverless 
+* [Traffic filters](docs-content://deploy-manage/security/ip-filtering-cloud.md) are not yet available on both ECH and Serverless.
 
 ## Billing
 
@@ -133,13 +136,9 @@ For the {{serverless-full}} trial, the rate limit is reduced to 15 MB/s and the
 ### Dynamic rate scaling for {{ech}}
 
 ```{applies_to}
-ess: preview
+ess:
 ```
 
-:::{note}
-This functionality is available in technical preview in {{ech}} deployments versions 9.2 and later.
-:::
-
 For {{ech}} deployments, rate limits can scale up or down dynamically based on backpressure from {{es}}. Every deployment starts with a 1 MB/s rate limit and 2 MB/s burst limit. The system automatically adjusts these limits based on your {{es}} capacity and load patterns. Scaling requires time, so sudden load spikes might still result in temporary rate limiting.
 
 ### Exceeding the rate limit