e7e6693926
Next PR will add a config setting that can be embedded in every component config. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com> |
||
|---|---|---|
| .. | ||
| testdata | ||
| README.md | ||
| batch_processor.go | ||
| batch_processor_test.go | ||
| config.go | ||
| config_test.go | ||
| factory.go | ||
| factory_test.go | ||
| metrics.go | ||
| metrics_test.go | ||
| splittraces.go | ||
| splittraces_test.go | ||
README.md
Batch Processor
Supported pipeline types: metric, traces, logs
The batch processor accepts spans, metrics, or logs and places them into batches. Batching helps better compress the data and reduce the number of outgoing connections required to transmit the data. This processor supports both size and time based batching.
It is highly recommended to configure the batch processor on every collector.
The batch processor should be defined in the pipeline after the memory_limiter
as well as any sampling processors. This is because batching should happen after
any data drops such as sampling.
Please refer to config.go for the config spec.
The following configuration options can be modified:
send_batch_size(default = 8192): Number of spans or metrics after which a batch will be sent.timeout(default = 200ms): Time duration after which a batch will be sent regardless of size.send_batch_max_size(default = 0): The maximum number of items in a batch. This property ensures that larger batches are split into smaller units. By default (0), there is no upper limit of the batch size. It is currently supported only for the trace pipeline.
Examples:
processors:
batch:
batch/2:
send_batch_size: 10000
timeout: 10s
Refer to config.yaml for detailed examples on using the processor.