diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index e88e731ee6777..626a920d30feb 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -711,7 +711,7 @@ menu: identifier: otel-setup-otlp-ingest parent: otel-setup-other weight: 4022 - - name: Agentless Deployment + - name: Direct OTLP Ingest url: /opentelemetry/setup/agentless identifier: otel-setup-intake-endpoint parent: otel-setup-other diff --git a/content/en/opentelemetry/_index.md b/content/en/opentelemetry/_index.md index 81491afb294da..e015dee543e01 100644 --- a/content/en/opentelemetry/_index.md +++ b/content/en/opentelemetry/_index.md @@ -132,7 +132,7 @@ If your applications and services are instrumented with OpenTelemetry libraries, ### Additional setup options -For other setup options, including Agentless deployment, see [Send Data to Datadog][7]. +For other setup options, including direct OTLP ingestion, see [Send Data to Datadog][7]. ## Further reading diff --git a/content/en/opentelemetry/compatibility.md b/content/en/opentelemetry/compatibility.md index ae84adc2f90e7..cbc8779103d09 100644 --- a/content/en/opentelemetry/compatibility.md +++ b/content/en/opentelemetry/compatibility.md @@ -13,52 +13,38 @@ Datadog offers multiple setup options to accommodate various use cases, from ful ## Setups -The following setups are supported: +Datadog supports several configurations for using OpenTelemetry. The primary difference between these setups is the choice of SDK (OpenTelemetry or Datadog) and the collector used to process and forward telemetry data. -| Setup Type | API | SDK | Collector/Agent | -|---------------------------------------------------------------|-------------|-------------------------|-----------------------------------------| -| **[Full OpenTelemetry][7]** | OTel API | OTel SDK | OTel Collector | -| **[OTel to Datadog Agent (OTLP)][6]** | OTel API | OTel SDK | Datadog Agent (OTLP Ingest) | -| **[OTel API with Datadog SDK and Agent][8]** | OTel API | Datadog SDK | Datadog Agent | -| **[Datadog Distribution of OTel Collector (DDOT)][9]** | OTel API | OTel SDK or Datadog SDK | Datadog Agent (with DDOT Collector) | -| **[Full Datadog][10]** | Datadog API | Datadog SDK | Datadog Agent | - -
The Datadog Distribution of OTel Collector supports two data flow options: -
  • OTel SDK → DDOT Collector, or
    • -
  • Datadog SDK → Datadog Agent
    • +| Setup Type | API | SDK | Collector/Agent | +|--------------------------------------------|-------------------------|-------------|-----------------------------------------------| +| [**Datadog SDK + DDOT (Recommended)**][29] | Datadog API or OTel API | Datadog SDK | Datadog Distribution of OTel Collector (DDOT) | +| [**OTel SDK + DDOT**][29] | OTel API | OTel SDK | Datadog Distribution of OTel Collector (DDOT) | +| [**OTel SDK + OSS Collector**][7] | OTel API | OTel SDK | OTel Collector (OSS) | +| [**Direct OTLP Ingest**][28] | OTel API | OTel SDK | N/A (Direct to Datadog endpoint) | ## Feature compatibility -### Supported Datadog features - -The following table shows Datadog feature compatibility across different setups: - -| Feature | Full OTel | OTel to Datadog Agent (OTLP) | OTel API with Datadog SDK and Agent | DDOT Collector | Full Datadog | -|-----------------------------------------------------|------------------------------------|------------------------------------|-------------------------------------|------------------------------------------------------|--------------| -| [Distributed Tracing][27] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Trace Metrics][26] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Correlated Traces, Metrics, Logs][19] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Runtime Metrics][23] | {{< X >}}
    (Java, .NET, Go only) | {{< X >}}
    (Java, .NET, Go only) | {{< X >}} | {{< X >}}
    (Java, .NET, Go only) | {{< X >}} | -| [Source code integration][24] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}}
    (Datadog SDK required) | {{< X >}} | -| [Real User Monitoring][22] (RUM) | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Cloud SIEM][18] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Cloud Network Monitoring][21] (CNM) | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Live Container Monitoring/Kubernetes Explorer][20] | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Live Processes][16] | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Universal Service Monitoring][17] (USM) | |{{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [App and API Protection][11] (AAP) | | | {{< X >}} | {{< X >}}
    (Datadog SDK required) | {{< X >}} | -| [Continuous Profiler][12] | | | {{< X >}} | {{< X >}}
    (Datadog SDK required) | {{< X >}} | -| [Data Jobs Monitoring][13] (DJM) | | | {{< X >}}
    (Datadog SDK required) | {{< X >}}
    (Datadog SDK required) | {{< X >}} | -| [Data Streams Monitoring][15] (DSM) | {{< tooltip text="N/A" tooltip="OTel does not offer DSM functionality" >}}| | {{< X >}} | {{< X >}} | {{< X >}} | -| [Database Monitoring][14] (DBM) | {{< tooltip text="N/A" tooltip="OTel does not offer DBM functionality" >}}| | {{< X >}}
    (Datadog SDK required) | {{< X >}}
    (Datadog SDK required) | {{< X >}} | - -### Supported OpenTelemetry features - -The following table shows OpenTelemetry feature compatibility across different setups: - -| Feature | Full OTel | OTel to Datadog Agent (OTLP) | OTel API with Datadog SDK and Agent | DDOT Collector | Full Datadog | -|-----------------------------------------------------|------------------------------------|------------------------------------|-------------------------------------|------------------------------------------------------|--------------| -| [Span Links][25] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | +The following table shows feature compatibility across different setups: + +| Feature | Datadog SDK + DDOT (Recommended) | OTel SDK + DDOT | OTel SDK + OSS Collector | Direct OTLP Ingest | +|---|---|---|---|---| +| [Cloud SIEM][18] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | +| [Correlated Traces, Metrics, Logs][19] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | +| [Distributed Tracing][27] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | +| [Real User Monitoring][22] (RUM) | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | +| [Runtime Metrics][23] | {{< X >}} | {{< X >}}
    (Java, .NET, Go only) | {{< X >}}
    (Java, .NET, Go only) | {{< X >}}
    (Java, .NET, Go only) | +| [Span Links][25] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | +| [Trace Metrics][26] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}}
    ({{< tooltip text="Sampled" tooltip="Trace metrics are calculated on the backend based on ingested spans that have passed through sampling, not on 100% of local traces before sampling." >}}) | +| [Cloud Network Monitoring][21] (CNM) | {{< X >}} | {{< X >}} | | | +| [Live Container Monitoring/Kubernetes Explorer][20] | {{< X >}} | {{< X >}} | | | +| [Live Processes][16] | {{< X >}} | {{< X >}} | | | +| [Universal Service Monitoring][17] (USM) | {{< X >}} | {{< X >}} | | | +| [App and API Protection][11] (AAP) | {{< X >}} | | | | +| [Continuous Profiler][12] | {{< X >}} | | | | +| [Data Jobs Monitoring][13] (DJM) | {{< X >}} | | | | +| [Data Streams Monitoring][15] (DSM) | {{< X >}} | | {{< tooltip text="N/A" tooltip="OTel does not offer DSM functionality" >}} | {{< tooltip text="N/A" tooltip="OTel does not offer DSM functionality" >}} | +| [Database Monitoring][14] (DBM) | {{< X >}} | | {{< tooltip text="N/A" tooltip="OTel does not offer DBM functionality" >}} | {{< tooltip text="N/A" tooltip="OTel does not offer DBM functionality" >}} | +| [Source code integration][24] | {{< X >}} | | | | ## More details @@ -76,10 +62,6 @@ Span-level or endpoint-level monitoring is **not** supported. For more information, see [Cloud Network Monitoring Setup][3]. -### Live Processes - -For **OTel to Datadog Agent (OTLP)**, you must enable the [Process Agent][4]. - ### Source Code Integration For unsupported languages in OpenTelemetry setups, [configure telemetry tagging][5] to link data to a specific commit. @@ -122,3 +104,5 @@ When using Datadog and OpenTelemetry together, Datadog recommends the following [25]: /tracing/trace_collection/span_links/ [26]: /tracing/metrics/metrics_namespace/ [27]: /tracing/trace_collection/ +[28]: /opentelemetry/setup/agentless +[29]: /opentelemetry/setup/ddot_collector \ No newline at end of file diff --git a/content/en/opentelemetry/reference/otel_metrics.md b/content/en/opentelemetry/reference/otel_metrics.md index a1900c7ba3516..d2537d89562bd 100644 --- a/content/en/opentelemetry/reference/otel_metrics.md +++ b/content/en/opentelemetry/reference/otel_metrics.md @@ -21,7 +21,7 @@ To send OpenTelemetry metrics to Datadog, you have three main options: - [OpenTelemetry Collector][11] - [Datadog Agent][12] -- [Agentless Deployment][13] +- [Direct OTLP Ingest][13] For more information about which setup is right for you, see [Send OpenTelemetry Data to Datadog][10]. diff --git a/content/en/opentelemetry/setup/_index.md b/content/en/opentelemetry/setup/_index.md index 2ac2b85334439..f13033f8ad4cd 100644 --- a/content/en/opentelemetry/setup/_index.md +++ b/content/en/opentelemetry/setup/_index.md @@ -46,7 +46,7 @@ Alternative methods are available for specific use cases, such as maintaining a Best for: Users on platforms other than Kubernetes Linux, or those who prefer a minimal configuration without managing Collector pipelines. {{< /nextlink >}} {{< nextlink href="/opentelemetry/setup/agentless" >}} -

    Agentless Deployment (Preview)

    +

    Direct OTLP Ingest (Preview)

    Best for: Situations requiring direct data transmission to Datadog's intake endpoint without any intermediary components. {{< /nextlink >}} {{< /whatsnext >}}