-
Notifications
You must be signed in to change notification settings - Fork 2.8k
kafkaexporter: inject client metadata into Kafka message headers #39130
New issue
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
Labels
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'd love to pick up this work and perhaps #39129 too since they're pretty closely related. |
marclop
added a commit
to marclop/opentelemetry-collector-contrib
that referenced
this issue
Apr 3, 2025
Adds a new config option specifying a list of metadata keys that should be propagated as Kafka message headers. Closes open-telemetry#39130 Signed-off-by: Marc Lopez Rubio <[email protected]>
Issue filed by code owner, removing |
Linked PR is now ready for review. |
dmathieu
pushed a commit
to dmathieu/opentelemetry-collector-contrib
that referenced
this issue
Apr 8, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds a new config option specifying a list of metadata keys that should be propagated as Kafka message headers. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#39130 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests added <!--Describe the documentation added.--> #### Documentation Updated the exporter's README. --------- Signed-off-by: Marc Lopez Rubio <[email protected]>
LucianoGiannotti
pushed a commit
to LucianoGiannotti/opentelemetry-collector-contrib
that referenced
this issue
Apr 9, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds a new config option specifying a list of metadata keys that should be propagated as Kafka message headers. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#39130 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests added <!--Describe the documentation added.--> #### Documentation Updated the exporter's README. --------- Signed-off-by: Marc Lopez Rubio <[email protected]>
Fiery-Fenix
pushed a commit
to Fiery-Fenix/opentelemetry-collector-contrib
that referenced
this issue
Apr 24, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds a new config option specifying a list of metadata keys that should be propagated as Kafka message headers. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#39130 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests added <!--Describe the documentation added.--> #### Documentation Updated the exporter's README. --------- Signed-off-by: Marc Lopez Rubio <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
exporter/kafka
Is your feature request related to a problem? Please describe.
I would like to propagate client metadata (e.g. a tenant ID) all the way to our backend. We have Kafka in the middle of our pipeline, like this:
otlpreceiver has
include_metadata
configuration which instructs it to record gPRC metadata (HTTP headers) as client metadata. This can be injected into out going requests using https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/headerssetterextensionNeither kafkareceiver nor kafkaexporter currently propagate client metadata.
Describe the solution you'd like
Add configuration to kafkaexporter for adding message headers based on client metadata, similar to headerssetterextension.
See also #39129
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: