-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
kafkaexporter
- support injecting headers
#33260
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
It may be preferable to add support for the headers setter extension to this exporter, but I'll defer to others who are better informed here than me. |
I will work on this issue. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
exporter/kafka
Is your feature request related to a problem? Please describe.
kafkareceiver does support header extraction, e.g.
However, kafkaexporter does not support injecting such headers, that could then be read by kafkareceiver.
Use case: we want to have a following setup: applications (send traces to) -> OT Collector -> Kafka -> Grafana Tempo. Grafana Tempo has multi-tenancy enabled, which means, that in order to identify which tenant sends the telemetry, an
X-Scope-OrgID
header is required.Note: Tempo is using kafkareceiver internally
Describe the solution you'd like
kafkaexporter should be able to inject custom headers that are in compatible format with what kafkareceiver expects. Config could look like this:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: