Batch OTLP requests
The following configuration example shows how you configure a Collector instance and its native batch processor to queue and batch OTLP requests and improve throughput performance.
For optimal performance of your Collector instance, we recommend that you apply this configuration with all setups.
If you use other processors, make sure the batch processor is configured last in your pipeline.
Prerequisites
- One of the following Collector distributions with the batch processor
- The Dynatrace Collector
- The OpenTelemetry Core or Contrib distribution
- A custom Builder version
- The API URL of your Dynatrace environment
- An API token with the relevant access scope
Demo configuration
receivers:otlp:protocols:grpc:http:processors:batch:send_batch_max_size: 1000timeout: 30ssend_batch_size : 800exporters:otlphttp:endpoint: ${env:DT_ENDPOINT}headers:Authorization: "Api-Token ${env:DT_API_TOKEN}"service:pipelines:traces:receivers: [otlp]processors: [batch]exporters: [otlphttp]metrics:receivers: [otlp]processors: [batch]exporters: [otlphttp]logs:receivers: [otlp]processors: [batch]exporters: [otlphttp]
Components
For our configuration, we configure the following components.
Receiver
Under receivers, we specify the standard otlp receiver as active receiver component for our Collector instance.
This is for demonstration purposes. You can specify any other valid receiver here (for example, zipkin).
Processor
Under processors, we specify the batch processor with the following parameters:
send_batch_max_sizeconfigured for a maximum of 1,000 entries per batchtimeoutconfigured to always send data after 30 seconds, regardless of any other batch limitssend_batch_sizeconfigured to always send data after 800 entries, regardless of any other batch limits
With this configuration, the Collector queues telemetry entries in batches and sends a batch either after 30 seconds have passed or at least 800 entries are queued.
We recommend the suggested configuration values above for most setups, but the optimal batch size may depend on your particular use case.
Be sure to configure the batch size to stay within the limits mentioned in Getting started or Dynatrace may reject requests.
Exporter
Under 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 endpoint and Authorization.
DT_ENDPOINTcontains the base URL of your ActiveGate (for example,https://{your-environment-id}.live.dynatrace.com/api/v2/otlp)DT_API_TOKENcontains the API token
Service pipeline
Under service, we assemble our receiver and exporter objects into pipelines for traces, metrics, and logs and enable our batch processor by referencing it under processors for each respective pipeline.
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: