---
title: Using Upstream OpenTelemetry SDKs
description: >-
  Deploy upstream OpenTelemetry SDKs with the OpenTelemetry Operator,
  application builds, or deployment automation, and send telemetry to Datadog.
breadcrumbs: >-
  Docs > OpenTelemetry in Datadog > Instrument Your Applications > Using
  Upstream OpenTelemetry SDKs
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Using Upstream OpenTelemetry SDKs

Upstream OpenTelemetry SDKs are maintained and supported by the OpenTelemetry community, and export telemetry with OTLP. Datadog supports their traces, metrics, and logs. Use upstream OpenTelemetry SDKs if your organization's policy allows only upstream OpenTelemetry components, or for languages that DDOT SDKs don't cover yet.

{% alert level="info" %}
Traces, metrics, and logs from upstream OpenTelemetry SDKs work in Datadog. Datadog-specific capabilities, such as Live Debugger, Dynamic Instrumentation, and SQL query-level Database Monitoring, require [DDOT SDKs](https://docs.datadoghq.com/opentelemetry/instrument/ddot_sdks.md). See [Feature Compatibility](https://docs.datadoghq.com/opentelemetry/compatibility.md) for details.
{% /alert %}

## Deployment methods{% #deployment-methods %}

An existing upstream OpenTelemetry SDK can send telemetry to Datadog without being replaced. For a new installation, follow the OpenTelemetry documentation for your environment and language.

To add Datadog-specific capabilities later, replace the upstream SDK with its [DDOT SDK](https://docs.datadoghq.com/opentelemetry/instrument/ddot_sdks.md) equivalent. Your OpenTelemetry API instrumentation and configuration stay the same.

| Environment                                        | Method                                                                                           | Best for                                                                                                        |
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| Kubernetes                                         | [OpenTelemetry Operator](https://opentelemetry.io/docs/platforms/kubernetes/operator/automatic/) | Centrally managed auto-instrumentation and configuration through Kubernetes resources and workload annotations. |
| Kubernetes, other containers, hosts, or serverless | [Language-specific SDK installation](https://opentelemetry.io/docs/languages/)                   | Installing the SDK or auto-instrumentation in the application build or deployment.                              |

## Send telemetry to Datadog{% #send-telemetry-to-datadog %}

For telemetry routing and setup instructions, see [Send OpenTelemetry Data to Datadog](https://docs.datadoghq.com/opentelemetry/setup.md). SDK installation and telemetry routing are separate choices. If your organization's policy allows only upstream OpenTelemetry components, use the [upstream OpenTelemetry Collector](https://docs.datadoghq.com/opentelemetry/setup/collector_exporter.md).

## View your telemetry{% #view-your-telemetry %}

View your application's traces in [Trace Explorer](https://docs.datadoghq.com/tracing/trace_explorer.md), metrics in [Metrics Explorer](https://docs.datadoghq.com/metrics/explorer.md), and logs in [Log Explorer](https://docs.datadoghq.com/logs/explorer.md). For missing telemetry, see [OpenTelemetry troubleshooting](https://docs.datadoghq.com/opentelemetry/troubleshooting.md).

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [OpenTelemetry language SDKs](https://opentelemetry.io/docs/languages/)
- [Send OpenTelemetry data to Datadog](https://docs.datadoghq.com/opentelemetry/setup.md)
- [OpenTelemetry feature compatibility](https://docs.datadoghq.com/opentelemetry/compatibility.md)
