datadog-agent --> otel-collector/datadog receiver

[nikhilleo07-bcdr]

Component(s)

receiver/datadog

Describe the issue you're reporting

Unable to receive traces in external Jeager dashboard while using Datadog Agent with OpenTelemetry Collector's Datadog receiver.

I am attempting to send traces from the Datadog Agent to two dashboards: Datadog and external Jaeger. The connection between Datadog Agent and OpenTelemetry Collector (otel-collector) appears to be is successful, as confirmed by the logs. I am using DD_URL environment variable in the Datadog Agent to configure the otel-collector URL.

Current Status:

• Traces are successfully being sent to the Datadog dashboard.
• No errors are appearing in the Datadog Agent logs.
• Traces are not being received in the OpenTelemetry Collector.

[github-actions]

Pinging code owners:

• receiver/datadog: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[lopes-felipe]

Hey @nikhilleo07-bcdr,

Let me know if I got this right:

• You have an application instrumented with a dd-trace library
• This application sends its traces to an instance of the datadog-agent
• This agent sends the traces both to Datadog's backend and to an OTel Collector via the datadog-receiver
• The Collector is then configured to send these traces to a Jaeger backend
• The traces are successfully exported to Datadog's backend but not to the Jaeger
• No errors are found anywhere in this chain

Is my understanding correct? If so, can you confirm how you are able to double-write those traces from the Datadog Agent? Because I don't think I'm familiar with such a capability.

Also, according to the agent's documentation, the DD_URL is only applicable for metrics. For traces, it looks like there is a specific config called apm_dd_url. Are you using that instead?

[lopes-felipe]

Also, the payload received in the dd-agent/datadog-receiver is considerable different from the one sent from the dd-agent/datadog-exporter to Datadog's backend, so I don't think you'll be able to achieve what you want with this approach.

My suggestion would be to try to send all your applications' traces solely to the OTel Collector/datadog-receiver and, from there, export them simultaneously to both Datadog and Jaeger backends. WDYT?