Collector use cases

Recommended configurations

When using the Collector, we recommend using the following features in the basic configuration, in addition to components specific to your use case.

• Batching—to improve network performance and throughput
• Memory Limitation—to avoid memory allocation related issues
• Enrichment—to include Kubernetes-specific information in your requests and support data correlation in the Dynatrace backend

Use cases

Prometheus

Configure the OpenTelemetry Collector to scrape your Prometheus data.

Zipkin

Configure the OpenTelemetry Collector to ingest and transform Zipkin data into Dynatrace.

Jaeger

Configure the OpenTelemetry Collector to ingest and transform Jaeger data into Dynatrace.

gRPC to HTTP

Configure the OpenTelemetry Collector to transform a gRPC OTLP request to HTTP.

Batching

Configure the OpenTelemetry Collector to send data in batches to the Dynatrace backend.

Memory Limitation

Configure the OpenTelemetry Collector to respect memory limits and not use excessive system resources.

Kubernetes Enrichment

Configure the OpenTelemetry Collector to enrich OTLP requests with Kubernetes data.