The following configuration example shows how to configure a Collector instance to send telemetry data to multiple backends at the same time.
receivers:otlp:protocols:grpc:endpoint: 0.0.0.0:4317http:endpoint: 0.0.0.0:4318exporters:otlphttp/dynatrace:endpoint: ${env:DT_ENDPOINT}headers:Authorization: "Api-Token ${env:DT_API_TOKEN}"otlp/coldstorage:endpoint: my.coldstorage.example:4317service:pipelines:traces:receivers: [otlp]processors: []exporters: [otlphttp/dynatrace, otlp/coldstorage]metrics:receivers: [otlp]processors: []exporters: [otlphttp/dynatrace, otlp/coldstorage]logs:receivers: [otlp]processors: []exporters: [otlphttp/dynatrace, otlp/coldstorage]
Validate your settings to avoid any configuration issues.
For our configuration, we configure the following components.
Under receivers
, we specify the otlp
receiver as the active receiver component for our Collector instance.
Under exporters
, we specify the following exporter instances for our backends.
otlphttp
exporter for Dynatraceotlp
exporter for the cold storage systemFor the Dynatrace exporter, we set the following two environment variables and reference them in the configuration values for endpoint
and Authorization
.
DT_ENDPOINT
contains the base URL of the Dynatrace API endpoint (for example, https://{your-environment-id}.live.dynatrace.com/api/v2/otlp
)DT_API_TOKEN
contains the API tokenUnder service
, we eventually assemble our receiver and exporter objects into pipelines, which accept any OTLP request (HTTP and gRPC) and forward it to the configured backends, using the configured exporters.
Data is ingested using the OpenTelemetry protocol (OTLP) via the Dynatrace OTLP APIs and is subject to the API's limits and restrictions. For more information see: