-
Notifications
You must be signed in to change notification settings - Fork 2.8k
exporter/kafka: add support for defining topic as request metadata #39208
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. |
This was referenced Apr 15, 2025
Issue filed by code owner, removing |
I've separated the message key support into #40149 |
I'll work on this issue to implement it as described. |
marclop
added a commit
to marclop/opentelemetry-collector-contrib
that referenced
this issue
May 20, 2025
Introduces a new per-signal config option `topic_from_metadata_key` to allow the user to produce to topics which which can be set using parts of the request metadata. This is useful for multi-tenant use-cases. Closes open-telemetry#39208 Signed-off-by: Marc Lopez Rubio <[email protected]>
dragonlord93
pushed a commit
to dragonlord93/opentelemetry-collector-contrib
that referenced
this issue
May 23, 2025
#### Description Introduces a new per-signal config option `topic_from_metadata_key` to allow the user to produce to topics which which can be set using parts of the request metadata. This is useful for multi-tenant use-cases. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Closes open-telemetry#39208 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests <!--Describe the documentation added.--> #### Documentation Updated the readme with the new option. --------- 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
Uh oh!
There was an error while loading. Please reload this page.
Component(s)
exporter/kafka
Is your feature request related to a problem? Please describe.
We have a need to route in tenant-specific Kafka topics, similar to the approach described at https://kafka.apache.org/documentation/#multitenancy-topic-naming.
There are arbitrarily many ways one might want to route data, and these apply to other components, so this is best left to another component -- see #39199 for a proposal. That proposal involves injecting the topic name into request metadata, which can then be referenced by the Kafka exporter.
Describe the solution you'd like
As described in #38888 (comment), I would like to introduce a configuration setting for extracting the topic name from request metadata.
Concretely, we should build on #39204 and introduce additional signal-specific
topic_from_metadata
settings (alternative name welcome).Describe alternatives you've considered
Originally I thought of making the topic name templated, as described in #38888.
Additional context
No response
The text was updated successfully, but these errors were encountered: