<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open Telemetry Collector on Dapr Docs</title><link>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/</link><description>Recent content in Open Telemetry Collector on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/index.xml" rel="self" type="application/rss+xml"/><item><title>Using OpenTelemetry Collector to collect traces</title><link>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector/</guid><description>&lt;p>Dapr directly writes traces using the OpenTelemetry (OTLP) protocol as the &lt;strong>recommended&lt;/strong> method. For observability tools that support the OTLP directly, it is recommended to use the &lt;a href="https://github.com/open-telemetry/opentelemetry-collector">OpenTelemetry Collector&lt;/a>, as it allows your application to quickly offload data and includes features, such as retries, batching, and encryption. For more information, read the Open Telemetry Collector &lt;a href="https://opentelemetry.io/docs/collector/#when-to-use-a-collector">documentation&lt;/a>.&lt;/p>
&lt;p>Dapr can also write traces using the Zipkin protocol. Prior to supporting the OTLP protocol, the Zipkin protocol was used with the OpenTelemetry Collector to send traces to observability tools such as AWS X-Ray, Google Cloud Operations Suite, and Azure Monitor. Both protocol approaches are valid, however the OpenTelemetry protocol is the recommended choice.&lt;/p></description></item><item><title>Using Dynatrace OpenTelemetry Collector to collect traces to send to Dynatrace</title><link>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector-dynatrace/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector-dynatrace/</guid><description>&lt;p>Dapr integrates with the &lt;a href="https://docs.dynatrace.com/docs/ingest-from/opentelemetry/collector">Dynatrace Collector&lt;/a> using the OpenTelemetry protocol (OTLP). This guide walks through an example using Dapr to push traces to Dynatrace, using the Dynatrace version of the OpenTelemetry Collector.&lt;/p>


&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note&lt;/h4>

 This guide refers to the Dynatrace OpenTelemetry Collector, which uses the same Helm chart as the open-source collector but overridden with the Dynatrace-maintained image for better support and Dynatrace-specific features.

&lt;/div>

&lt;h2 id="prerequisites">Prerequisites&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/operations/hosting/kubernetes/">Install Dapr on Kubernetes&lt;/a>&lt;/li>
&lt;li>Access to a Dynatrace tenant and an API token with &lt;code>openTelemetryTrace.ingest&lt;/code>, &lt;code>metrics.ingest&lt;/code>, and &lt;code>logs.ingest&lt;/code> scopes&lt;/li>
&lt;li>Helm&lt;/li>
&lt;/ul>
&lt;h2 id="set-up-dynatrace-opentelemetry-collector-to-push-to-your-dynatrace-instance">Set up Dynatrace OpenTelemetry Collector to push to your Dynatrace instance&lt;/h2>
&lt;p>To push traces to your Dynatrace instance, install the Dynatrace OpenTelemetry Collector on your Kubernetes cluster.&lt;/p></description></item><item><title>Using OpenTelemetry Collector to collect traces to send to App Insights</title><link>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector-appinsights/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector-appinsights/</guid><description>&lt;p>Dapr integrates with &lt;a href="https://github.com/open-telemetry/opentelemetry-collector">OpenTelemetry (OTEL) Collector&lt;/a> using the OpenTelemetry protocol (OTLP). This guide walks through an example using Dapr to push traces to Azure Application Insights, using the OpenTelemetry Collector.&lt;/p>
&lt;h2 id="prerequisites">Prerequisites&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/operations/hosting/kubernetes/">Install Dapr on Kubernetes&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/azure/azure-monitor/app/create-workspace-resource">Create an Application Insights resource&lt;/a> and make note of your Application Insights connection string.&lt;/li>
&lt;/ul>
&lt;h2 id="set-up-otel-collector-to-push-to-your-app-insights-instance">Set up OTEL Collector to push to your App Insights instance&lt;/h2>
&lt;p>To push traces to your Application Insights instance, install the OpenTelemetry Collector on your Kubernetes cluster.&lt;/p></description></item><item><title>Using OpenTelemetry to send traces to Jaeger V2</title><link>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger/</guid><description>&lt;p>Dapr supports writing traces using the OpenTelemetry (OTLP) protocol, and Jaeger V2 natively supports OTLP, allowing Dapr to send traces directly to a Jaeger V2 instance. This approach is recommended for production to leverage Jaeger V2&amp;rsquo;s capabilities for distributed tracing.&lt;/p>






&lt;ul class="nav nav-tabs" id="tabs-0" role="tablist">
 &lt;li class="nav-item">
 &lt;button class="nav-link active"
 id="tabs-00-00-tab" data-bs-toggle="tab" data-bs-target="#tabs-00-00" role="tab"
 data-td-tp-persist="self-hosted" aria-controls="tabs-00-00" aria-selected="true">
 Self-hosted
 &lt;/button>
 &lt;/li>&lt;li class="nav-item">
 &lt;button class="nav-link"
 id="tabs-00-01-tab" data-bs-toggle="tab" data-bs-target="#tabs-00-01" role="tab"
 data-td-tp-persist="kubernetes" aria-controls="tabs-00-01" aria-selected="false">
 Kubernetes
 &lt;/button>
 &lt;/li>
&lt;/ul>

&lt;div class="tab-content" id="tabs-0-content">
 &lt;div class="tab-body tab-pane fade show active"
 id="tabs-00-00" role="tabpanel" aria-labelled-by="tabs-00-00-tab" tabindex="0">
 &lt;h2 id="configure-jaeger-v2-in-self-hosted-mode">Configure Jaeger V2 in self-hosted mode&lt;/h2>
&lt;h3 id="local-setup">Local setup&lt;/h3>
&lt;p>The simplest way to start Jaeger is to run the pre-built, all-in-one Jaeger image published to DockerHub and expose the OTLP port:&lt;/p></description></item></channel></rss>