Indicate that we don't support OpenTelemetry Collector and Datadog Ag…

…ent on same host (DataDog#22069) * Remove alongside the Agent instructions. * Remove option of Datadog Agent and Collector on same host; add note that we don't support this. * Apply suggestions from code review Co-authored-by: jhgilbert <[email protected]> --------- Co-authored-by: jhgilbert <[email protected]>
clemherreman · Mar 7, 2024 · 414ae03 · 414ae03
1 parent 77873a5
commit 414ae03
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 64 deletions.
diff --git a/content/en/opentelemetry/collector_exporter/otel_collector_datadog_exporter.md b/content/en/opentelemetry/collector_exporter/otel_collector_datadog_exporter.md
@@ -584,68 +584,6 @@ To use the OpenTelemetry Operator:
 [3]: /opentelemetry/otel_collector_datadog_exporter/?tab=kubernetesgateway#4-run-the-collector
 
 {{% /tab %}}
-
-{{% tab "Alongside the Agent" %}}
-
-To use the OpenTelemetry Collector alongside the Datadog Agent:
-
-1. Set up an additional DaemonSet to ensure that the Datadog Agent runs on each host alongside the previously set up [OpenTelemetry Collector DaemonSet][1]. For information, read [the docs about deploying the Datadog Agent in Kubernetes][2].
-
-2. Enable [OTLP ingestion in the Datadog Agent][3].
-
-3. Now that the Datadog Agent is ready to receive OTLP traces, logs, and metrics, change your [OpenTelemetry Collector DaemonSet][1] to use the [OTLP exporter][4] instead of the Datadog Exporter by adding the following configuration to [your config map][5]:
-
-   ```yaml
-   # ...
-   exporters:
-     otlp:
-       endpoint: "${HOST_IP}:4317"
-       tls:
-         insecure: true
-   # ...
-   ```
-
-4. Make sure that the `HOST_IP` environment variable is provided [in the DaemonSet][6]:
-
-   ```yaml
-   # ...
-           env:
-           - name: HOST_IP
-             valueFrom:
-               fieldRef:
-                 fieldPath: status.hostIP
-   # ...
-   ```
-
-5. Make sure that the [service pipelines][7] are using OTLP:
-
-   ```yaml
-   # ...
-       service:
-         pipelines:
-           metrics:
-             receivers: [otlp]
-             processors: [resourcedetection, k8sattributes, batch]
-             exporters: [otlp]
-           traces:
-             receivers: [otlp]
-             processors: [resourcedetection, k8sattributes, batch]
-             exporters: [otlp]
-   # ...
-   ```
-
-   In this case, don't use the `hostmetrics` receiver because those metrics will be emitted by the Datadog Agent.
-
-[1]: /opentelemetry/otel_collector_datadog_exporter/?tab=kubernetesdaemonset#4-run-the-collector
-[2]: /containers/kubernetes/
-[3]: /opentelemetry/otlp_ingest_in_the_agent/?tab=kubernetesdaemonset#enabling-otlp-ingestion-on-the-datadog-agent
-[4]: https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/otlpexporter/README.md#otlp-grpc-exporter
-[5]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/2c32722e37f171bab247684e7c07e824429a8121/exporter/datadogexporter/examples/k8s-chart/configmap.yaml#L15
-[6]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/2c32722e37f171bab247684e7c07e824429a8121/exporter/datadogexporter/examples/k8s-chart/daemonset.yaml#L33
-[7]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/2c32722e37f171bab247684e7c07e824429a8121/exporter/datadogexporter/examples/k8s-chart/configmap.yaml#L30-L39
-
-{{% /tab %}}
-
 {{< /tabs >}}
 
 

diff --git a/content/en/opentelemetry/ingestion_sampling_with_opentelemetry.md b/content/en/opentelemetry/ingestion_sampling_with_opentelemetry.md
@@ -18,10 +18,11 @@ further_reading:
 ## Overview
 
 If your applications and services are instrumented with OpenTelemetry libraries, you can: 
-- Send traces to the **[OpenTelemetry collector][1]**, and use the Datadog exporter to forward them to Datadog
-- Send traces to the **[OpenTelemetry collector alongside the Datadog Agent][2]**, which then forwards them to Datadog.
+- Send traces to the **[OpenTelemetry Collector][1]**, and use the Datadog exporter to forward them to Datadog.
 - Send traces to the **[Datadog Agent OTLP ingest][3]**, which forwards them to Datadog.
 
+**Note**: Datadog doesn't support running the OpenTelemetry Collector and the Datadog Agent on the same host.
+
 In the first and second scenario, [APM RED metrics][4] (request/errors counts and latency distributions by service, operation and resource) are computed in the Datadog Exporter. In the third case, the Datadog Agent computes these metrics.
 
 {{< img src="/opentelemetry/guide/ingestion_otel/otel_apm_metrics_computation.png" alt="Otel APM Metrics computation" style="width:100%;" >}}