Datadog tracing libraries provide an implementation of the OpenTelemetry API for instrumenting your code. This means you can maintain vendor-neutral instrumentation of your services, while still taking advantage of Datadog’s native implementation, features, and products.

Diagram: OpenTelemetry API with DD tracing libraries sends data through OTLP protocol to the Datadog Agent, which forwards to Datadog's platform.

Note: You can also send your OpenTelemetry API instrumented traces to Datadog using the OTel Collector.

By instrumenting your code with OpenTelemetry APIs, your code:

  • Remains free of vendor-specific API calls.
  • Does not depend on Datadog tracing libraries at compile time (only runtime).

Replace the OpenTelemetry SDK with the Datadog tracing library in the instrumented application, and the traces produced by your running code can be processed, analyzed, and monitored alongside Datadog traces and in Datadog proprietary products such as Continuous Profiler, Data Streams Monitoring, Application Security Management, and Live Processes.

To learn more, follow the link for your language:

Java
Python
Ruby
go
Node.js
PHP
.Net

To see which Datadog features are supported with this setup, see the feature compatibility table under OTel API with Datadog SDK and Agent.

Further reading