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
- Kubernetes Enrichment—to include Kubernetes-specific information in your requests and support data correlation in the Dynatrace backend
Use cases
Batching
Configure the OpenTelemetry Collector to send data in batches to the Dynatrace backend.
FluentD
Configure the OpenTelemetry Collector to ingest data from FluentD.
gRPC to HTTP
Configure the OpenTelemetry Collector to transform a gRPC OTLP request to HTTP.
Histogram summaries
Configure the OpenTelemetry Collector to compute bucket summaries for histogram metrics.
Jaeger
Configure the OpenTelemetry Collector to ingest and transform Jaeger data into Dynatrace.
Kubernetes Enrichment
Configure the OpenTelemetry Collector to enrich OTLP requests with Kubernetes data.
Log files
Configure the OpenTelemetry Collector to ingest log files.
Memory Limitation
Configure the OpenTelemetry Collector to respect memory limits and not use excessive system resources.
Multiple backends
Configure the OpenTelemetry Collector to export to multiple backends.
Prometheus
Configure the OpenTelemetry Collector to scrape your Prometheus data.
Sampling
Configure the OpenTelemetry Collector to sample distributed traces.
StatsD
Configure the OpenTelemetry Collector to ingest StatsD data.
Syslog
Configure the OpenTelemetry Collector to ingest syslog data.
Zipkin
Configure the OpenTelemetry Collector to ingest and transform Zipkin data into Dynatrace.
