Ingest data from Jaeger
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.
receivers: jaeger: protocols: grpc: exporters: otlphttp: endpoint: $DT_ENDPOINT/api/v2/otlp headers: Authorization: "Api-Token $DT_API_TOKEN" service: pipelines: traces: receivers: [jaeger] exporters: [otlphttp]
- Contrib distribution or a custom Builder version with the Jaeger receiver
- The API URL of your Dynatrace environment
- An API token with the relevant access scope
For our configuration, we configure the following components.
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, we specify the default
otlphttp 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
DT_ENDPOINTcontains the base URL of your ActiveGate (for example,
DT_API_TOKENcontains the API token
service, we eventually assemble our receiver and exporter objects into a traces pipeline, which will handle our Jaeger transformation to OTLP.