We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
exporter/kafka
In this issue #35686 it was described a usecase that would require a complete record generated by OpenTelemetry Collector to be send in a RAW format. Unfortunatelly, the current raw format sends just body (https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/kafkaexporter/raw_marshaler.go#L31).
raw
Add an encoding, that would not limit the raw format to just body, but will also send resource and record attributes.
Save the whole 'message' to a variable and replace a Body with a content of this variable. It seems to me it will be resource consuming.
Creating a follow-up issue recommended by @ChrsMark in #35686 (comment)
The text was updated successfully, but these errors were encountered:
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Sorry, something went wrong.
Triage: Issue appears to contain necessary information. Moving to waiting-for-codeowners
waiting-for-codeowners
No branches or pull requests
Component(s)
exporter/kafka
Is your feature request related to a problem? Please describe.
In this issue #35686 it was described a usecase that would require a complete record generated by OpenTelemetry Collector to be send in a RAW format. Unfortunatelly, the current
raw
format sends just body (https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/kafkaexporter/raw_marshaler.go#L31).Describe the solution you'd like
Add an encoding, that would not limit the
raw
format to just body, but will also send resource and record attributes.Describe alternatives you've considered
Save the whole 'message' to a variable and replace a Body with a content of this variable. It seems to me it will be resource consuming.
Additional context
Creating a follow-up issue recommended by @ChrsMark in #35686 (comment)
The text was updated successfully, but these errors were encountered: