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
**Description:** Add support for encoding extensions in the
kafkaexporter
To be able to use encoding extensions this PR adds extension support and
proposes to rename the existing `encoding` configuration property to
`format` and reusing the `encoding` property for configuring encoding
extensions. Reason is to be consistent with other receivers/exporters.
Related to
open-telemetry#33888
which adds encoding extension support in the `kafkareceiver`.
**Link to tracking Issue:** n/a
**Testing:** Tested via the following configuration.
```
receivers:
kafka:
brokers:
- localhost:29092
encoding: json
group_id: test1
topic: logs_in
extensions:
json_log_encoding:
exporters:
debug:
verbosity: detailed
kafka:
brokers:
- localhost:29092
encoding: json_log_encoding
topic: json_out
processors:
batch:
service:
extensions: [json_log_encoding]
pipelines:
logs:
receivers: [kafka]
processors: [batch]
exporters: [debug, kafka]
telemetry:
logs:
level: "info"
```
Any json can be written to the `logs_in` topic and results be viewed in
the `json_out` topic.
When removing `encoding: json_log_encoding` the default format type is
used and the output in `json_out` topic changes accordingly.
**Documentation:** Updated README.md within the receiver describing the
use of encoding extensions.
Co-authored-by: Sean Marciniak <[email protected]>
0 commit comments