-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New component: Concurrent Batch Processor #33422
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
We have decided (and begun) to upstream concurrent batch processor support in the core repository. |
The purpose and use-cases of the new component
This component is an experimental processor, forked from the core
OpenTelemetry Collector
batchprocessor
component.
This component enhances the batchprocessor with
until the request returns with success or an error status code.
in-memory size of each request it admits to the pipeline and
otherwise stalls requests until they timeout.
as needed to send batches through the pipeline.
This processor should be used to
Example configuration for the component
Telemetry data types supported
Traces, metrics, and logs supported.
Is this a vendor-specific component?
Code Owner(s)
@jmacd, @moh-osman3
Sponsor (optional)
No response
Additional context
This component currently lives in the
otel-arrow
repository https://github.com/open-telemetry/otel-arrow/tree/main/collector/processor/concurrentbatchprocessor. Migrating this component to contrib might be helpful for other collector users who are experiencing issues with exporterhelper's lack of backpressure, error propagation, and high memory usage. This has been used in production for the past 6 months now and used in our arrow collector pipelines with the Otel Arrow receiver and exporter. This has helped us improve issues faced when using exporterhelper with queueing enabled.The text was updated successfully, but these errors were encountered: