Using OpenTelemetry Collector to collect traces

    Dapr will be exporting trace in the OpenTelemetry format when OpenTelemetry is GA. In the mean time, traces can be exported using the Zipkin format. Combining with the OpenTelemetry Collector you can still send trace to many popular tracing backends (like Azure AppInsights, AWS X-Ray, StackDriver, etc).

    1. A installation of Dapr on Kubernetes.

    2. You are already setting up your trace backends to receive traces.

    1. Check out the file and replace the section marked with with the correct settings for your trace exporter. Again, refer to the OpenTelemetry Collector links in the Prerequisites section to determine the correct settings.

    2. Apply the configuration with .

    Next, set up both a Dapr configuration file to turn on tracing and deploy a tracing exporter component that uses the OpenTelemetry Collector.

    1. Create a collector-config.yaml file with this content

    When running in Kubernetes mode, apply the configuration by adding a annotation to the container that you want to participate in the distributed tracing, as shown in the following example:

    Some of the quickstarts such as already configure these settings, so if you are using those no additional settings are needed.

    That’s it! There’s no need include any SDKs or instrument your application code. Dapr automatically handles the distributed tracing for you.

    Last modified January 1, 0001