Send data to multiple backends
The following configuration example shows how to configure a Collector instance to send telemetry data to multiple backends at the same time.
Prerequisites
- One of the following Collector distributions
- The Dynatrace Collector
- OpenTelemetry Core or Contrib
- A custom Builder version
- For Dynatrace
The ingest URLs and any applicable authentication credentials for the other backends
Demo configuration
receivers:otlp:protocols:grpc:http:exporters: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]exporters: [otlphttp/dynatrace, otlp/coldstorage]metrics:receivers: [otlp]exporters: [otlphttp/dynatrace, otlp/coldstorage]logs:receivers: [otlp]exporters: [otlphttp/dynatrace, otlp/coldstorage]
Components
For our configuration, we configure the following components.
Receiver
Under receivers
, we specify the otlp
receiver as the active receiver component for our Collector instance.
Exporter
Under exporters
, we specify the following exporter instances for our backends.
- An
otlphttp
exporter for Dynatrace - A gRPC
otlp
exporter for the cold storage system
For 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 your ActiveGate (for example,https://{your-environment-id}.live.dynatrace.com/api/v2/otlp
)DT_API_TOKEN
contains the API token
Service pipeline
Under 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.
Limits and limitations
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: