How-To: Set up Datadog for distributed tracing

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.

1. Add your Datadog API key to the ./deploy/opentelemetry-collector-generic-datadog.yaml file in the datadog exporter configuration section:

   data:
     otel-collector-config:
       ...
       exporters:
         ...
         datadog:
           api:
             key: <YOUR_API_KEY>

2. Apply the opentelemetry-collector configuration by running the following command.

   kubectl apply -f ./deploy/open-telemetry-collector-generic-datadog.yaml

3. 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

4. Apply the appconfig configuration by adding a dapr.io/config annotation to the container that you want to participate in the distributed tracing.

   annotations:
      dapr.io/config: "appconfig"

5. Create and configure the application. Once running, telemetry data is sent to Datadog and visible in Datadog APM.

Related Links/References

• Complete example of setting up Dapr on a Kubernetes cluster
• Datadog documentation about OpenTelemetry support
• Datadog Application Performance Monitoring

Last modified March 21, 2024: Merge pull request #4082 from newbe36524/v1.13 (f4b0938)