History

Bogdan Drutu aa67926c69 Move issuegenerator to cmd so go mod tidy resolves dependencies (#1284 ) Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>		2020-07-07 20:00:17 -07:00
..
testdata	Switch batch_processor to internal data model (#832 )	2020-04-15 16:51:27 -07:00
README.md	Decentralize component documentation (#1089 )	2020-06-05 11:33:32 -07:00
batch_processor.go	Add batch size metric (#1241 )	2020-07-07 16:30:22 -07:00
batch_processor_test.go	Move issuegenerator to cmd so go mod tidy resolves dependencies (#1284 )	2020-07-07 20:00:17 -07:00
config.go	Remove year from copyright (#964 )	2020-05-26 12:44:22 -04:00
config_test.go	Remove year from copyright (#964 )	2020-05-26 12:44:22 -04:00
factory.go	Add the ability to batch metrics as a processor. (#1060 )	2020-06-02 10:23:26 -07:00
factory_test.go	Add the ability to batch metrics as a processor. (#1060 )	2020-06-02 10:23:26 -07:00
metrics.go	Add batch size metric (#1241 )	2020-07-07 16:30:22 -07:00

README.md

Batch Processor

Supported pipeline types: metric, traces

The batch processor accepts spans or metrics 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.

Examples:

processors:
  batch:
  batch/2:
    send_batch_size: 10000
    timeout: 10s

Refer to config.yaml for detailed examples on using the processor.