Ingest Jaeger data with the OTel Collector

• Latest Dynatrace
• How-to guide
• 1-min read
• Updated on Aug 04, 2026

The following configuration example shows how you configure a Collector instance to accept Jaeger data, transform it to OTLP, and send it to the Dynatrace backend.

Prerequisites

See Collector Deployment and Collector Configuration on how to set up your Collector with the configuration below.

Demo configuration

receivers:
  jaeger:
    protocols:
      grpc:

exporters:
  otlp_http:
    endpoint: ${env:DT_ENDPOINT}
    headers:
      Authorization: "Bearer ${env:DT_PLATFORM_TOKEN}"

service:
  pipelines:
    traces:
      receivers: [jaeger]
      processors: []
      exporters: [otlp_http]

receivers:
  jaeger:
    protocols:
      grpc:

exporters:
  otlp_http:
    endpoint: ${env:DT_ENDPOINT}
    headers:
      Authorization: "Api-Token ${env:DT_API_TOKEN}"

service:
  pipelines:
    traces:
      receivers: [jaeger]
      processors: []
      exporters: [otlp_http]

Components

For our configuration, we configure the following components.

Receivers

Under receivers, we specify the jaeger receiver as active receiver component for our Collector instance.

The Jaeger receiver can be customized with a few more attributes, which we leave with their default values in our example.

Exporters

Under exporters, we specify the default otlp_http exporter and configure it with our Dynatrace API URL and the required authentication token.

For this purpose, we set the following two environment variables and reference them in the configuration values for endpoint and Authorization.

Service pipelines

Under service, we eventually assemble our receiver and exporter objects into a traces pipeline, which will handle our Jaeger transformation to OTLP.