Overview

OpenTelemetry (OTel) provides standardized protocols for collecting and routing telemetry data. Datadog supports multiple ways to collect and analyze telemetry data from OpenTelemetry-instrumented applications, whether you’re using existing Datadog infrastructure or prefer a vendor-neutral setup.

Why OpenTelemetry with Datadog?

Datadog provides advanced observability for all your application telemetry, regardless of its source. By supporting OpenTelemetry, Datadog offers:

• Flexibility and choice: Use standardized instrumentation while maintaining freedom to adapt as your technology needs evolve.
• Comprehensive language support: Consistently monitor applications across your entire tech stack.
• Unified instrumentation: Maintain a single approach to instrumentation across your systems.
• Powerful analytics: Combine OpenTelemetry’s standardization with Datadog’s robust analysis, visualization, and alerting capabilities.

Whether you’re already using OpenTelemetry or considering adoption, Datadog provides flexible options to meet your needs.

Key decisions

There are two key decisions to make when using OpenTelemetry with Datadog:

• How to instrument your applications
• How to send your data to Datadog

The features available to you depend on these choices. For example, using the OpenTelemetry API with the Datadog SDK provides access to more Datadog features than using the OpenTelemetry SDK alone.

For more information, read Feature Compatibility.

Instrument your applications

There are several ways to instrument your applications with OpenTelemetry and Datadog. Each approach provides different features and levels of vendor neutrality.

• Full OpenTelemetry: Use the OpenTelemetry SDK and API for a vendor-neutral setup.
• OpenTelemetry API: Use the OpenTelemetry API with Datadog’s SDK implementation.
• OpenTelemetry instrumentation libraries: Extend Datadog’s observability to additional frameworks and technologies.

For more information, see Instrument Your Applications.

Send OpenTelemetry data to Datadog

If your applications and services are instrumented with OpenTelemetry libraries, you can choose how to get traces, metrics, and logs data into Datadog.

Option 1: Use the OpenTelemetry Collector

Best for: New or existing OTel users wanting a completely vendor-neutral setup.

• Complete vendor neutrality for sending OpenTelemetry data to Datadog
• Flexible configuration options like tail-based sampling and data transformations

Option 2: Use the Datadog Agent

Best for: Existing Datadog users or teams requiring Agent-based features such as:

• Fleet Automation
• Live Container Monitoring
• Kubernetes Explorer
• Live Processes
• Cloud Network Monitoring
• Universal Service Monitoring
• 850+ Datadog integrations

Additional setup options

For other setup options, including direct OTLP intake, see Send Data to Datadog.

Further reading

추가 유용한 문서, 링크 및 기사:

Feature CompatibilityDOCUMENTATION Instrument Your ApplicationsDOCUMENTATION Send Data to DatadogDOCUMENTATION Datadog's partnership with OpenTelemetryBLOG Monitor OpenTelemetry-instrumented apps with support for W3C Trace ContextBLOG Send metrics and traces from OpenTelemetry Collector to Datadog via Datadog ExporterBLOG Forward logs from the OpenTelemetry Collector with the Datadog ExporterBLOG OTLP ingestion in the AgentBLOG Learn more about AWS's managed Lambda Layer for OpenTelemetryBLOG Correlate Datadog RUM events with traces from OpenTelemetry-instrumented applicationsBLOG Monitor runtime metrics from OTel-instrumented apps with Datadog APMBLOG Introduction to OpenTelemetry with DatadogLEARNING CENTER