Move SDK OTLP export docs to Using Datadog SDK page (Preview) (#37689)

* Move SDK OTLP export content to Using Datadog SDK page

Feature OTLP export on the dd_sdks landing page and demote the
OpenTelemetry API content to a subsection. Add prerequisites and a
verification step, scope Preview to traces, and alias the old private
page URL.

* Remove unrelated files accidentally staged

* Add Next steps routing to Send Data to Datadog from OTLP export

* Trim duplicate DDOT recommendation from Next steps

* Fix OTLP export link, drop redundant Next steps, trim API section, move API aliases

* Surface OTLP export in OTel instrument hub, add page description and compatibility link

* Restructure SDK OTLP docs as a hub with a dedicated OTLP export page

* Mirror sibling hub-page card layout on the SDK landing page

* Add page description, reorder SDK nav, expand landing page hub

* Scope OTLP export docs to traces and reframe SDK hub

* Tighten trace-export wording: scope Preview callout, collector-first intro

* Update content/en/opentelemetry/instrument/dd_sdks/_index.md

Co-authored-by: Zach Montoya <zach.montoya@datadoghq.com>

* Add SDK prerequisite and OTLP protocol defaults note

* Refine OTLP protocol note wording

* Polish OTLP docs wording per review feedback

---------

Co-authored-by: Zach Montoya <zach.montoya@datadoghq.com>

Author: brett0000FF

config/_default/menus/main.en.yaml

@@ -702,20 +702,25 @@ menu:
       identifier: otel-dd-sdk-parent
       parent: otel-instrumentation
       weight: 302
-    - name: Configuration
-      url: opentelemetry/config/environment_variable_support/
-      identifier: otel_env_var
+    - name: OTLP Export
+      url: /opentelemetry/instrument/dd_sdks/otlp_trace_export/
+      identifier: otel-otlp-export-dd-sdk
       parent: otel-dd-sdk-parent
-      weight: 3021
+      weight: 3020
     - name: APIs
       url: /opentelemetry/instrument/dd_sdks/api_support
       identifier: otel-api-dd-sdk
       parent: otel-dd-sdk-parent
-      weight: 3022
+      weight: 3021
     - name: Instrumentation Libraries
       url: /opentelemetry/instrument/dd_sdks/instrumentation_libraries/
       identifier: otel_instrumentation_libraries
       parent: otel-dd-sdk-parent
+      weight: 3022
+    - name: Configuration
+      url: opentelemetry/config/environment_variable_support/
+      identifier: otel_env_var
+      parent: otel-dd-sdk-parent
       weight: 3023
     - name: Send Data to Datadog
       identifier: otel_collect

content/en/opentelemetry/instrument/_index.md

@@ -1,5 +1,6 @@
 ---
 title: Instrument Your Applications
+description: Instrument your applications with OpenTelemetry and Datadog SDKs to collect, visualize, and analyze traces across your services and infrastructure.
 aliases:
     - /opentelemetry/guide/otel_api_tracing_interoperability
 further_reading:
@@ -24,9 +25,10 @@ Datadog supports several approaches for instrumenting your applications with Ope
 
 Integrating Datadog with OpenTelemetry allows you to use Datadog's comprehensive observability platform while leveraging OpenTelemetry's vendor-agnostic instrumentation. This allows you to collect, visualize, and analyze traces from your applications and infrastructure.
 
-Use the OpenTelemetry Tracing APIs with Datadog's SDK to maintain vendor-neutral instrumentation while accessing Datadog's full feature set.
+Use the OpenTelemetry Tracing APIs with Datadog's SDK to maintain vendor-neutral instrumentation while accessing Datadog's full feature set. Datadog SDKs can also export traces in OpenTelemetry Protocol (OTLP) format to an OTLP-compatible receiver.
 
 {{< whatsnext desc=" " >}}
+    {{< nextlink href="/opentelemetry/instrument/dd_sdks/otlp_trace_export/" >}}Export traces from the Datadog SDK in OTLP format{{< /nextlink >}}
     {{< nextlink href="/opentelemetry/instrument/api_support" >}}Use the Datadog SDK with OpenTelemetry API{{< /nextlink >}}
     {{< nextlink href="/opentelemetry/config/environment_variable_support/" >}}Configure the Datadog SDK with OpenTelemetry SDK environment variables{{< /nextlink >}}
 {{< /whatsnext >}}

content/en/opentelemetry/instrument/dd_sdks/_index.md

@@ -1,10 +1,10 @@
 ---
-title: OpenTelemetry API Support
-aliases:
-  - /opentelemetry/interoperability/api_support
-  - /opentelemetry/interoperability/otel_api_tracing_interoperability/
-  - /opentelemetry/instrument/api_support/
+title: Using Datadog SDKs with OpenTelemetry
+description: Export telemetry in OTLP format from Datadog SDKs, or use the OpenTelemetry API with Datadog SDKs to keep vendor-neutral instrumentation.
 further_reading:
+    - link: '/opentelemetry/setup/ddot_collector/'
+      text: 'Datadog Distribution of the OpenTelemetry Collector (DDOT)'
+      tag: 'Documentation'
     - link: 'tracing/guide/instrument_custom_method'
       text: 'Instrument a custom method to get deep visibility into your business logic'
       tag: 'Documentation'
@@ -21,44 +21,37 @@ algolia:
   tags: ['otel custom instrumentation']
 ---
 
-Datadog SDKs provide an implementation of the [OpenTelemetry API][1] for traces, metrics, and logs. This means you can maintain vendor-neutral instrumentation of your services, while still taking advantage of Datadog's native implementation, features, and products. 
-
-The telemetry produced by your running code can be processed, analyzed, and monitored alongside Datadog's native telemetry, allowing you to take advantage of Datadog's unified platform and products like [Continuous Profiler][3], [Data Streams Monitoring][4], [App and API Protection][5], and [Live Processes][6].
-
-{{< img src="/opentelemetry/setup/otel-api-dd-sdk.png" alt="Diagram: OpenTelemetry API with Datadog SDKs sends telemetry data through the OTLP protocol to the Datadog Agent, which forwards to Datadog's platform." style="width:100%;" >}}
-
-**Note:** You can also send your OpenTelemetry API instrumented traces to Datadog using the [OTel Collector][7].
-
-By [instrumenting your code with OpenTelemetry APIs][2], your code:
-
-- Remains free of vendor-specific API calls.
-- Does not depend on Datadog SDKs at compile time (only runtime).
-
-To learn more, follow the link for your language:
-
-{{< card-grid card_width="170px">}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=java" src="integrations_logos/java.png" alt="Java" >}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=python" src="integrations_logos/python.png" alt="Python" >}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=ruby" src="integrations_logos/ruby.png" alt="Ruby" >}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=go" src="integrations_logos/go-metro.png" alt="go" >}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=node_js" src="integrations_logos/nodejs.png" alt="Node.js" >}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=php" src="integrations_logos/php.png" alt="PHP" >}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=dot_net" src="integrations_logos/dotnet_text.png" alt=".Net" >}}
-  {{< image-card href="/opentelemetry/instrument/dd_sdks/api_support/?prog_lang=rust" src="integrations_logos/rust.png" alt="Rust" >}}
-{{< /card-grid >}}
-
-<br>
-
-<div class="alert alert-info">To see which Datadog features are supported with this setup, see the <a href="/opentelemetry/compatibility/#feature-compatibility">feature compatibility table.</a></div>
+Datadog SDKs work with OpenTelemetry in two independent ways. Exporting telemetry in [OpenTelemetry Protocol (OTLP)][1] format controls how telemetry is sent. The [OpenTelemetry API][2] controls how you instrument your services. These can be enabled separately, but using them together provides an OpenTelemetry-native experience.
+
+{{< whatsnext desc=" " >}}
+    {{< nextlink href="/opentelemetry/instrument/dd_sdks/otlp_trace_export/" >}}
+    <h3>Export traces in OTLP format</h3>
+    Export traces from a Datadog SDK in OTLP format to DDOT or any OpenTelemetry Collector, instead of sending them to the Datadog Agent. In Preview.
+    {{< /nextlink >}}
+    {{< nextlink href="/opentelemetry/instrument/dd_sdks/api_support/" >}}
+    <h3>Use the OpenTelemetry API</h3>
+    Instrument your services with vendor-neutral OpenTelemetry APIs while taking advantage of Datadog's native features and products.
+    {{< /nextlink >}}
+{{< /whatsnext >}}
+
+<div class="alert alert-info"><strong>Comparing setups?</strong><br> See the <a href="/opentelemetry/compatibility/#feature-compatibility">feature compatibility table</a> to understand which Datadog features each setup supports.</div>
+
+## Configure and extend
+
+{{< whatsnext desc=" " >}}
+    {{< nextlink href="/opentelemetry/instrument/dd_sdks/instrumentation_libraries/" >}}
+    <h3>Instrumentation Libraries</h3>
+    Add OpenTelemetry instrumentation libraries to capture telemetry from third-party components alongside Datadog SDK instrumentation.
+    {{< /nextlink >}}
+    {{< nextlink href="/opentelemetry/config/environment_variable_support/" >}}
+    <h3>Configuration</h3>
+    Configure Datadog SDKs with OpenTelemetry SDK environment variables.
+    {{< /nextlink >}}
+{{< /whatsnext >}}
 
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: https://opentelemetry.io/docs/specs/otel/trace/api/
-[2]: /tracing/trace_collection/otel_instrumentation/
-[3]: /profiler/
-[4]: /data_streams/
-[5]: /security/application_security/
-[6]: /infrastructure/process
-[7]: /opentelemetry/setup/collector_exporter/
+[1]: https://opentelemetry.io/docs/specs/otlp/
+[2]: https://opentelemetry.io/docs/specs/otel/trace/api/

content/en/opentelemetry/instrument/dd_sdks/api_support.mdoc.md

@@ -4,6 +4,7 @@ description: "Use the OpenTelemetry API with Datadog SDKs to send traces, metric
 aliases:
   - /opentelemetry/interoperability/api_support
   - /opentelemetry/interoperability/otel_api_tracing_interoperability/
+  - /opentelemetry/instrument/api_support/
   - /opentelemetry/instrument/api_support/dotnet/
   - /opentelemetry/instrument/api_support/dotnet/logs
   - /opentelemetry/instrument/api_support/dotnet/metrics

content/en/opentelemetry/instrument/dd_sdks/otlp_trace_export.md

@@ -1,25 +1,30 @@
 ---
 title: Export Traces from Datadog SDKs in OTLP Format
-private: true
+description: Configure a Datadog SDK to export traces in OpenTelemetry Protocol (OTLP) format to a DDOT Collector or any OTLP-compatible receiver.
 further_reading:
-- link: "/opentelemetry/instrument/dd_sdks/"
-  tag: "Documentation"
-  text: "OpenTelemetry API Support in Datadog SDKs"
-- link: "/opentelemetry/"
-  tag: "Documentation"
-  text: "OpenTelemetry Support in Datadog"
-- link: "/tracing/"
-  tag: "Documentation"
-  text: "Datadog APM"
+    - link: '/opentelemetry/instrument/dd_sdks/'
+      text: 'Using Datadog SDKs with OpenTelemetry'
+      tag: 'Documentation'
+    - link: '/opentelemetry/setup/ddot_collector/'
+      text: 'Datadog Distribution of the OpenTelemetry Collector (DDOT)'
+      tag: 'Documentation'
+    - link: '/tracing/'
+      text: 'Datadog APM'
+      tag: 'Documentation'
 ---
 
 {{< callout url="#" btn_hidden="true" header="Preview">}}
-OTLP trace export is in Preview. To provide feedback or request support, contact your Datadog account team.
+OTLP trace export from Datadog SDKs is in Preview. To provide feedback or request support, contact your Datadog account team.
 {{< /callout >}}
 
-## Overview
+Datadog SDKs can export traces in [OTLP][1] format to an OTLP-compatible receiver, including [DDOT][2] or any OpenTelemetry Collector.
 
-Datadog SDKs support exporting traces in [OpenTelemetry Protocol (OTLP)][3] format to any OTLP-compliant receiver or backend, including [DDOT][1] or any OpenTelemetry Collector.
+## Prerequisites
+
+OTLP export requires:
+
+- **The Datadog SDK installed and attached to your service.** OTLP export uses your existing Datadog SDK setup. You don't need to configure the Datadog Agent for native trace export, because OTLP export sends traces to a receiver instead.
+- **An OTLP-compatible receiver that forwards data to Datadog**, such as the [DDOT Collector][2] or an [OpenTelemetry Collector][3]. OTLP export sends data to a receiver rather than directly to Datadog, so the receiver must be reachable from your instrumented service. For production workloads, Datadog recommends DDOT for batching, performance, and processing benefits. You aren't required to use DDOT.
 
 ## Language support
 
@@ -54,6 +59,8 @@ Select your language to see the minimum SDK version and supported OTLP protocols
 
 {{< /programming-lang-wrapper >}}
 
+**Note**: The OpenTelemetry specification defaults OTLP to `http/protobuf`, but Datadog SDK defaults vary by language. Python, Node.js, and .NET default to `http/json`, while Java and Go default to `http/protobuf`. Where a language supports multiple protocols, set `OTEL_EXPORTER_OTLP_PROTOCOL` or `OTEL_EXPORTER_OTLP_TRACES_PROTOCOL` to override the default. Make sure your receiver accepts the protocol you use. By convention, OTLP/HTTP (`http/protobuf` or `http/json`) uses port `4318`, and OTLP/gRPC (`grpc`) uses port `4317`.
+
 ## Enable OTLP trace export
 
 To export traces in OTLP format, set the following environment variables on the instrumented service:
@@ -65,17 +72,27 @@ DD_TRACE_OTEL_ENABLED=true
 
 By default, traces are sent to `http://localhost:4318/v1/traces`.
 
-To send traces to a different endpoint, set `OTEL_EXPORTER_OTLP_ENDPOINT` or the trace-specific `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`. See the [OTLP Exporter Configuration][2] documentation for details.
+To send traces to a different endpoint, set `OTEL_EXPORTER_OTLP_ENDPOINT` or the trace-specific `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`. See the [OTLP Exporter Configuration][4] documentation for details.
+
+## Verify
+
+After you enable OTLP export and your service receives traffic, confirm that traces appear in the [Trace Explorer][5]. If traces don't arrive, verify that your [receiver][6] is running, reachable at the configured endpoint, and forwarding data to Datadog.
 
 ## Current limitations
 
 - OTLP trace export is in Preview and supports core APM functionality for automatic and manually created traces. Other Datadog features and capabilities may not be supported, or may require the Datadog Agent even if traces are not sent through it.
-- Traces are exported with Datadog semantics. For example an HTTP status code is represented as `http.status_code` in Datadog semantics and `http.response.status_code` in OTel semantics.
+- Traces are exported with Datadog semantics. For example, an HTTP status code is represented as `http.status_code` in Datadog semantics and `http.response.status_code` in OTel semantics.
+
+For details on which Datadog features each setup supports, see the [feature compatibility table][7].
 
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /opentelemetry/setup/ddot_collector/
-[2]: https://opentelemetry.io/docs/specs/otel/protocol/exporter/
-[3]: https://opentelemetry.io/docs/specs/otlp/
+[1]: https://opentelemetry.io/docs/specs/otlp/
+[2]: /opentelemetry/setup/ddot_collector/
+[3]: /opentelemetry/setup/collector_exporter/
+[4]: https://opentelemetry.io/docs/specs/otel/protocol/exporter/
+[5]: /tracing/trace_explorer/
+[6]: /opentelemetry/setup/
+[7]: /opentelemetry/compatibility/#feature-compatibility