You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Spawn otelcol receivers on need.
Spawning a receiver for every signal for every receiver component was not needed and created errors with the kafka receivers. Now the otelcol receiver checks which signals are needed and spawn the corresponding receivers.
* changelog entry
* add warning when more than one signal is set for the output of the kafka receiver
* cleanup
* use validate instead of logging
* update doc
* add test to checkt that the receiver spawns the correct receivers on update
* doc typo
* remove default value in code
* update tests
* Update docs/sources/reference/components/otelcol.receiver.kafka.md
Co-authored-by: Paulin Todev <[email protected]>
* Update internal/component/otelcol/receiver/kafka/kafka.go
Co-authored-by: Paulin Todev <[email protected]>
* Update docs/sources/reference/components/otelcol.receiver.kafka.md
Co-authored-by: Paulin Todev <[email protected]>
* adapt tests
* make test more readable
---------
Co-authored-by: Paulin Todev <[email protected]>
returnfmt.Errorf("only one signal can be set in the output block when a Kafka topic is explicitly set; currently set signals: %s", strings.Join(signals, ", "))
require.ErrorContains(t, args.Validate(), "only one signal can be set in the output block when a Kafka topic is explicitly set; currently set signals: logs, traces")
require.ErrorContains(t, args.Validate(), "only one signal can be set in the output block when a Kafka topic is explicitly set; currently set signals: logs, metrics, traces")
0 commit comments