Promote OTEL based ingestion but put the OTLP/HTTP endpoint under advanced topics

Author: felixbarny

manage-data/data-store/data-streams/quickstart-tsds.md

@@ -13,6 +13,12 @@ Use this quickstart to set up a time series data stream (TSDS), ingest a few doc
 
 A _time series_ is a sequence of data points collected at regular time intervals. For example, you might track CPU usage or stock price over time. This quickstart uses simplified weather sensor readings to show how a TSDS helps you analyze metrics data over time. 
 
+::::{note}
+If you're looking to ingest OpenTelemetry metrics,
+follow the [OpenTelemetry quickstarts](/solutions/observability/get-started/opentelemetry/quickstart/index.md).
+This allows you to start sending data into a TSDS without having to worry about manually setting up data streams or configuring mappings.
+::::
+
 ## Prerequisites
 
 * Access to [{{dev-tools-app}} Console](/explore-analyze/query-filter/tools/console.md) in {{kib}}, or another way to make {{es}} API requests
@@ -315,7 +321,6 @@ This quickstart introduced the basics of time series data streams. To learn more
 
 * [](/manage-data/data-store/data-streams/time-series-data-stream-tsds.md)
 * [](/manage-data/data-store/data-streams/set-up-tsds.md)
-* [](/manage-data/data-store/data-streams/tsds-ingest-otlp.md)
 
 For more information about the APIs used in this quickstart, review the {{es}} API reference documentation:
 

manage-data/data-store/data-streams/set-up-tsds.md

@@ -14,8 +14,9 @@ products:
 This page shows you how to manually set up a [time series data stream](/manage-data/data-store/data-streams/time-series-data-stream-tsds.md) (TSDS).
 
 ::::{note}
-For a simplified setup that doesn't require manually mapping dimension and metric fields via index templates,
-have a look at the [OpenTelemetry Protocol (OTLP)-based data ingestion](tsds-ingest-otlp.md).
+If you're looking to ingest OpenTelemetry metrics,
+follow the [OpenTelemetry quickstarts](/solutions/observability/get-started/opentelemetry/quickstart/index.md).
+This allows you to start sending data into a TSDS without having to worry about manually setting up data streams or configuring mappings.
 ::::
 
 ## Before you begin [tsds-prereqs]

manage-data/data-store/data-streams/tsds-ingest-otlp.md

@@ -1,12 +1,18 @@
 ---
-navigation_title: "Ingest OTLP metrics"
+navigation_title: "OTLP/HTTP endpoint"
 applies_to:
   stack: preview 9.2
 products:
   - id: elasticsearch
 ---
 
-# Ingest metrics using the OpenTelemetry Protocol (OTLP)
+# OTLP/HTTP endpoint
+
+:::{important}
+Usually, you'll want to send data to an OpenTelemetry Collector or the [{{motlp}}](opentelemetry:/reference/motlp.md),
+rather than directly going to the {{es}} OTLP endpoint.
+See [Best practices](#best-practices) for more details.
+:::
 
 In addition to the ingestion of metrics data through the bulk API,
 {{es}} offers an alternative way to ingest data via the [OpenTelemetry Protocol (OTLP)](https://opentelemetry.io/docs/specs/otlp).
@@ -25,10 +31,6 @@ Ingesting metrics data using the OTLP endpoint has the following advantages:
   there's no need to manually create data streams, index templates, or define dimensions and metrics.
   Metrics are dynamically mapped using the metadata included in the OTLP requests.
 
-:::{important}
-On {{ecloud}} , use the [{{motlp}}](opentelemetry:/reference/motlp.md) instead of connecting directly to the {{es}} OTLP endpoint.
-:::
-
 ## How to send data to the OTLP endpoint
 
 To send data from an OpenTelemetry Collector to the {{es}} OTLP endpoint,
@@ -69,7 +71,9 @@ use the [OpenTelemetry language SDK](https://opentelemetry.io/docs/getting-start
 
 ## Best practices
 
-Do not send metrics from applications directly to the {{es}} OTLP endpoint, especially if there are many individual applications that periodically send a small amount of metrics. Instead, send data to an OpenTelemetry Collector first. This helps with handling many connections, and with creating bigger batches to improve ingestion performance. For more details on the recommended way to set up OpenTelemetry-based data ingestion, refer to the [EDOT reference architecture](opentelemetry:/reference/architecture/index.md).
+Do not send metrics from applications directly to the {{es}} OTLP endpoint, especially if there are many individual applications that periodically send a small amount of metrics. Instead, send data to an OpenTelemetry Collector first. This helps with handling many connections, and with creating bigger batches to improve ingestion performance. On {{ecloud}}, use the [{{motlp}}](opentelemetry:/reference/motlp.md) and for self-managed use cases, you can use the [Elastic Distribution of OpenTelemetry Collector](elastic-agent:/reference/edot-collector/index.md).
+
+For more details on the recommended way to set up OpenTelemetry-based data ingestion, refer to the [EDOT reference architecture](opentelemetry:/reference/architecture/index.md).
 
 ## Send data to different data streams
 

manage-data/toc.yml

@@ -15,7 +15,6 @@ toc:
             children:
               - file: data-store/data-streams/quickstart-tsds.md
               - file: data-store/data-streams/set-up-tsds.md
-              - file: data-store/data-streams/tsds-ingest-otlp.md
               - file: data-store/data-streams/downsampling-time-series-data-stream.md
                 children:
                 - file: data-store/data-streams/downsampling-concepts.md
@@ -25,6 +24,7 @@ toc:
                 children:
                 - file: data-store/data-streams/time-bound-tsds.md
                 - file: data-store/data-streams/reindex-tsds.md
+                - file: data-store/data-streams/tsds-ingest-otlp.md
           - file: data-store/data-streams/logs-data-stream.md
           - file: data-store/data-streams/failure-store.md
             children: