Configure Dapr to send distributed tracing data

Configure Dapr to send distributed tracing data

It is recommended to run Dapr with tracing enabled for any production scenario. You can configure Dapr to send tracing and telemetry data to many backends based on your environment, whether it is running in the cloud or on-premises.

Tracing configuration

The tracing section under the Configuration spec contains the following properties:

  1. tracing:
  2. tracing:
  3. samplingRate: "1"
  4. zipkin:
  5. endpointAddress: "https://..."

The following table lists the properties for tracing:

PropertyTypeDescription
samplingRatestringSet sampling rate for tracing to be enabled or disabled.
zipkin.endpointAddressstringSet the Zipkin server address.

Zipkin in self hosted mode

The following steps show you how to configure Dapr to send distributed tracing data to Zipkin running as a container on your local machine and view them.

For self hosted mode, create a Dapr configuration file locally and reference it with the Dapr CLI.

  1. Create the following config.yaml YAML file:

    1. apiVersion: dapr.io/v1alpha1
    2. kind: Configuration
    3. metadata:
    4. name: zipkin
    5. namespace: default
    6. spec:
    7. tracing:
    8. samplingRate: "1"
    9. zipkin:
    10. endpointAddress: "http://localhost:9411/api/v2/spans"
  2. Launch Zipkin using Docker:

    1. docker run -d -p 9411:9411 openzipkin/zipkin
  3. Launch Dapr with the --config param with the path for where the config.yaml is saved :

    1. dapr run --app-id mynode --app-port 3000 --config ./config.yaml node app.js

Zipkin in Kubernetes mode

The following steps show you how to configure Dapr to send distributed tracing data to Zipkin running as a container in your Kubernetes cluster, and how to view them.

Setup

First, deploy Zipkin:

  1. kubectl create deployment zipkin --image openzipkin/zipkin

Create a Kubernetes Service for the Zipkin pod:

  1. kubectl expose deployment zipkin --type ClusterIP --port 9411

Next, create the following YAML file locally:

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Configuration
  3. metadata:
  4. name: zipkin
  5. namespace: default
  6. spec:
  7. tracing:
  8. samplingRate: "1"
  9. zipkin:
  10. endpointAddress: "http://zipkin.default.svc.cluster.local:9411/api/v2/spans"

Finally, deploy the Dapr configuration:

  1. kubectl apply -f config.yaml

In order to enable this configuration for your Dapr sidecar, add the following annotation to your pod spec template:

  1. annotations:
  2. dapr.io/config: "zipkin"

That’s it! Your sidecar is now configured for use with Zipkin.

Viewing Tracing Data

To view traces, connect to the Zipkin service and open the UI:

  1. kubectl port-forward svc/zipkin 9411:9411

On your browser, go to http://localhost:9411 and you should see the Zipkin UI.

zipkin

References

Last modified March 18, 2021: Merge pull request #1321 from dapr/aacrawfi/logos (9a399d5)