The documentation you are viewing is for Dapr v1.13 which is an older version of Dapr. For up-to-date documentation, see the latest version.
How-To: Set up Datadog for distributed tracing
Dapr captures metrics and traces that can be sent directly to Datadog through the OpenTelemetry Collector Datadog exporter.
Configure Dapr tracing with the OpenTelemetry Collector and Datadog
Using the OpenTelemetry Collector Datadog exporter, you can configure Dapr to create traces for each application in your Kubernetes cluster and collect them in Datadog.
Before you begin, set up the OpenTelemetry Collector.
-
Add your Datadog API key to the
./deploy/opentelemetry-collector-generic-datadog.yaml
file in thedatadog
exporter configuration section:data: otel-collector-config: ... exporters: ... datadog: api: key: <YOUR_API_KEY>
-
Apply the
opentelemetry-collector
configuration by running the following command.kubectl apply -f ./deploy/open-telemetry-collector-generic-datadog.yaml
-
Set up a Dapr configuration file that will turn on tracing and deploy a tracing exporter component that uses the OpenTelemetry Collector.
kubectl apply -f ./deploy/collector-config.yaml
-
Apply the
appconfig
configuration by adding adapr.io/config
annotation to the container that you want to participate in the distributed tracing.annotations: dapr.io/config: "appconfig"
-
Create and configure the application. Once running, telemetry data is sent to Datadog and visible in Datadog APM.
![Datadog APM showing telemetry data.](/images/datadog-traces.png)
Related Links/References
- Complete example of setting up Dapr on a Kubernetes cluster
- Datadog documentation about OpenTelemetry support
- Datadog Application Performance Monitoring
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.