opentelemetry-collector-contrib
opentelemetry-collector-contrib copied to clipboard
[receiver/kafkareceiver] Add otlp_json support in kafka receiver
Description: <Describe what has changed.>
The current features dont support otlp_json in receivers/kafkareceivers.Add support for otlp_json which accepts json formated for Otel Collector kafka receiver Link to tracking Issue: <Issue number if applicable> #33627
Testing: <Describe what testing was performed and which tests were added.> Added test files for the same.
Documentation: <Describe the documentation added.>
this is a draft in process, would love to see if im going in the right direction or not.
@joeyyy09 check the linter failures
kafkareceiver/unmarshaler.go:61: File is not gci-ed with --skip-generated -s standard -s default -s prefix(github.com/open-telemetry/opentelemetry-collector-contrib) (gci)
@joeyyy09 check the linter failures
kafkareceiver/unmarshaler.go:61: File is notgci-ed with --skip-generated -s standard -s default -s prefix(github.com/open-telemetry/opentelemetry-collector-contrib) (gci)
My bad, fixed that.
Support for encoding extensions in the kafkareceiver was just merged with https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33888. Using the otlpencodingextension should now do the job.
Prom tests are failing on main, not an issue here (https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/35119). Everything else in the PR is green. @open-telemetry/collector-maintainers this can be merged.
@thmshmm I think an upgrade to otlpencodingextension is an independent issue and can be tackled separately, there's no need for it to block this PR.