otelcol.processor.batch: new component #2333
Conversation
Introduce a `otelcol.processor.batch` component which wraps around the upstream batch processor. Closes grafana#2285.
rfratto
force-pushed
the
otelcol.processor.batch
branch
from
d60c1ac to
dfde58e
Compare
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
docs/sources/flow/reference/components/otelcol.processor.batch.md
Outdated
Show resolved
Hide resolved
| default, telemetry data will be dropped. To send telemetry data to other | ||
| components, configure the `metrics`, `logs`, and `traces` arguments | ||
| accordingly. | ||
|
|
There was a problem hiding this comment.
Is it OK that we don't have examples for otelcol.processor.batch and otelcol.processor.batch?
There was a problem hiding this comment.
Yeah, I'm planning on adding examples after #2288 is implemented (since that would allow examples for an entire pipeline of OpenTelemetry Collector components)
| SendBatchMaxSize uint32 `river:"send_batch_max_size,attr,optional"` | ||
|
|
||
| // Output configures where to send processed data. Required. | ||
| Output *otelcol.ConsumerArguments `river:"output,block"` |
There was a problem hiding this comment.
Do we want to reuse the forward_to terminology we used for Prometheus, or is this more in-line with what OTel does?
There was a problem hiding this comment.
Maybe, I think we need to think about it after we have a good set of otelcol components in. It might make sense for us to use different terminology just to help prevent confusing things (i.e., assume that you can use forward_to to send data to a prometheus.* receiver)
github-actions
bot
added
the
frozen-due-to-age
PR Description
Introduce a new
otelcol.processor.batchcomponent.Which issue(s) this PR fixes
Closes #2285.
Notes to the Reviewer
PR Checklist