Rename Managed inputs section: motlp → managed-inputs

docs/redirects.yml

@@ -4,8 +4,15 @@ redirects:
   'reference/edot-cloud-forwarder/azure/index.md': 'edot-cloud-forwarder-azure://reference/edot-cf-azure/index.md'
   'reference/edot-cloud-forwarder/gcp.md': 'reference/edot-cloud-forwarder/gcp/index.md'
 
-  # Managed OTLP Endpoint (mOTLP page moved to a sub-page under the new Managed inputs landing)
-  'reference/motlp.md': 'reference/motlp/managed-otlp-endpoint.md'
+  # Managed inputs: the section folder was renamed from motlp to managed-inputs.
+  # The historical /motlp URL served the Managed OTLP Endpoint, so point it (and the
+  # short-lived landing URL) there; every other page maps to its managed-inputs equivalent.
+  'reference/motlp.md': 'reference/managed-inputs/managed-otlp-endpoint.md'
+  'reference/motlp/index.md': 'reference/managed-inputs/managed-otlp-endpoint.md'
+  'reference/motlp/managed-otlp-endpoint.md': 'reference/managed-inputs/managed-otlp-endpoint.md'
+  'reference/motlp/prometheus-remote-write.md': 'reference/managed-inputs/prometheus-remote-write.md'
+  'reference/motlp/rate-limiting.md': 'reference/managed-inputs/rate-limiting.md'
+  'reference/motlp/troubleshooting.md': 'reference/managed-inputs/troubleshooting.md'
 
   # EDOT Collector troubleshooting pages (from reference to troubleshooting)
   'reference/edot-collector/troubleshooting/index.md': 'docs-content://troubleshoot/ingest/opentelemetry/edot-collector/index.md'

docs/reference/architecture/hosts_vms.md

@@ -31,7 +31,7 @@ The following sections outline the recommended architectures for different Elast
 :::::{applies-switch}
 
 ::::{applies-item} serverless:
-{{serverless-full}} provides a [Managed OTLP Endpoint](/reference/motlp/managed-otlp-endpoint.md) for ingestion of OpenTelemetry data.
+{{serverless-full}} provides a [Managed OTLP Endpoint](/reference/managed-inputs/managed-otlp-endpoint.md) for ingestion of OpenTelemetry data.
 
 ![VM-Serverless](../images/host-serverless.png)
 
@@ -44,7 +44,7 @@ Users can send data direct from the Collectors or SDKs deployed on the edge envi
 You need an {{ech}} deployment version 9.0 or later.
 :::
 
-{{ech}} provides a [Managed OTLP Endpoint](/reference/motlp/managed-otlp-endpoint.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.
+{{ech}} provides a [Managed OTLP Endpoint](/reference/managed-inputs/managed-otlp-endpoint.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.
 
 ![VM-ech](../images/host-ech.png)
 ::::

docs/reference/architecture/index.md

@@ -60,7 +60,7 @@ When a Collector in gateway mode is deployed, it is considered part of the {{pro
 
 The need for an EDOT Collector in gateway mode as part of your Elastic backend depends on your deployment type:
 
-**{{serverless-full}} and {{ech}}**: Edge collectors can send OTLP data directly to the [Managed OTLP Endpoint](/reference/motlp/managed-otlp-endpoint.md) without requiring a self-managed Gateway Collector. The Managed OTLP Endpoint provides a fully managed ingestion layer as part of the Elastic backend. 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.
+**{{serverless-full}} and {{ech}}**: Edge collectors can send OTLP data directly to the [Managed OTLP Endpoint](/reference/managed-inputs/managed-otlp-endpoint.md) without requiring a self-managed Gateway Collector. The Managed OTLP Endpoint provides a fully managed ingestion layer as part of the Elastic backend. 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.
 
 **Self-managed, ECE, and ECK deployments**: An EDOT Collector in gateway mode is **required as part of your {{product.observability}} backend**. This Gateway Collector exposes the OTLP endpoint that edge collectors send data to, and handles essential preprocessing, including:
 

docs/reference/architecture/k8s.md

@@ -60,7 +60,7 @@ The following sections outline the recommended architectures for different Elast
 :::::{applies-switch}
 
 ::::{applies-item} serverless:
-{{serverless-full}} provides a [Managed OTLP Endpoint](/reference/motlp/managed-otlp-endpoint.md) for ingestion of OpenTelemetry data.
+{{serverless-full}} provides a [Managed OTLP Endpoint](/reference/managed-inputs/managed-otlp-endpoint.md) for ingestion of OpenTelemetry data.
 
 ![K8s-Serverless](../images/k8s-serverless.png)
 
@@ -73,7 +73,7 @@ For a Kubernetes setup, the gateway Collector in your cluster sends OTLP data di
 You need an {{ech}} deployment version 9.0 or later.
 :::
 
-{{ech}} provides a [Managed OTLP Endpoint](/reference/motlp/managed-otlp-endpoint.md) for ingestion of OpenTelemetry data.
+{{ech}} provides a [Managed OTLP Endpoint](/reference/managed-inputs/managed-otlp-endpoint.md) for ingestion of OpenTelemetry data.
 
 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.
 

docs/reference/compatibility/edot-vs-upstream.md

@@ -73,7 +73,7 @@ Due to current upstream limitations, some capabilities are temporarily available
 Upstream OTel SDKs are technically [Compatible] with Elastic and can send data through the same ingestion paths, but Elastic does not provide official support or troubleshooting assistance for them. Refer to the [SDK compatibility table](sdks.md) for version-level details.
 
 :::{important}
-EDOT SDKs are designed to export telemetry through the [EDOT Collector](elastic-agent://reference/edot-collector/index.md) or the [{{motlp}}](/reference/motlp/managed-otlp-endpoint.md). Using EDOT SDKs directly with {{product.apm-server}}'s OpenTelemetry intake is not supported — attribute mapping, enrichment, and processing pipelines are not guaranteed on that path.
+EDOT SDKs are designed to export telemetry through the [EDOT Collector](elastic-agent://reference/edot-collector/index.md) or the [{{motlp}}](/reference/managed-inputs/managed-otlp-endpoint.md). Using EDOT SDKs directly with {{product.apm-server}}'s OpenTelemetry intake is not supported — attribute mapping, enrichment, and processing pipelines are not guaranteed on that path.
 :::
 
 ## Kubernetes Operator
@@ -88,7 +88,7 @@ On platforms that provide their own OpenTelemetry distributions, such as [Red Ha
 
 ## EDOT Cloud Forwarders
 
-The [EDOT Cloud Forwarders](/reference/edot-cloud-forwarder/index.md) are Elastic-specific components with no upstream equivalent. They package the EDOT Collector as a cloud function — AWS Lambda, Azure Function, or GCP Cloud Run — to collect telemetry from cloud provider services such as S3, CloudWatch, Blob Storage, Event Hub, GCS, and GCP Operations, and forward it to the [{{motlp}}](/reference/motlp/managed-otlp-endpoint.md).
+The [EDOT Cloud Forwarders](/reference/edot-cloud-forwarder/index.md) are Elastic-specific components with no upstream equivalent. They package the EDOT Collector as a cloud function — AWS Lambda, Azure Function, or GCP Cloud Run — to collect telemetry from cloud provider services such as S3, CloudWatch, Blob Storage, Event Hub, GCS, and GCP Operations, and forward it to the [{{motlp}}](/reference/managed-inputs/managed-otlp-endpoint.md).
 
 Because there is no upstream counterpart, the EDOT-versus-upstream comparison does not apply to Cloud Forwarders. Refer to the [EDOT Cloud Forwarder documentation](/reference/edot-cloud-forwarder/index.md) for setup guides and supported cloud services.
 

docs/reference/compatibility/limitations.md

@@ -33,7 +33,7 @@ Refer to [EDOT data streams compared to classic APM](../compatibility/data-strea
 
 ## Centralized parsing and processing of data
 
-With OTel-native ingestion of data, for example through the EDOT Collector or the [Managed OTLP endpoint](/reference/motlp/managed-otlp-endpoint.md), [{{es}} Ingest Pipelines](docs-content://manage-data/ingest/transform-enrich/ingest-pipelines.md) are not supported.
+With OTel-native ingestion of data, for example through the EDOT Collector or the [Managed OTLP endpoint](/reference/managed-inputs/managed-otlp-endpoint.md), [{{es}} Ingest Pipelines](docs-content://manage-data/ingest/transform-enrich/ingest-pipelines.md) are not supported.
 
 The OTel-native data format in {{es}} contains dotted fields. Ingest Pipeline processors can't access fields that have a dot in their name without having previously transformed the dotted field into an object using the [`Dot expander processor`](elasticsearch://reference/enrich-processor/dot-expand-processor.md).
 

docs/reference/edot-sdks/index.md

@@ -79,7 +79,7 @@ This table provides an overview of the features available in the {{edot}} (EDOT)
 
 ## 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](elastic-agent://reference/edot-collector/index.md) or the [{{motlp}}](/reference/motlp/managed-otlp-endpoint.md) to ingest data into Elastic solutions from the EDOT SDKs. Other ingestion paths are not officially supported by Elastic.
+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](elastic-agent://reference/edot-collector/index.md) or the [{{motlp}}](/reference/managed-inputs/managed-otlp-endpoint.md) to ingest data into Elastic solutions from the EDOT SDKs. Other ingestion paths are not officially supported by Elastic.
 
 Using EDOT SDKs directly with {{product.apm-server}}'s OpenTelemetry intake endpoint is not supported.  
 While some data might ingest, Elastic doesn't guarantee:

docs/reference/toc.yml

@@ -1,3 +1,3 @@
 project: 'Elastic Distributions of OpenTelemetry (EDOT)'
 toc:
   - file: index.md
@@ -19,7 +19,7 @@
       - file: compatibility/limitations.md
       - file: compatibility/nomenclature.md
       - file: compatibility/data-streams.md 
-  - toc: motlp
+  - toc: managed-inputs
   - file: data-streams.md
   - file: central-configuration.md
   - file: edot-sdks/index.md