-
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
Kafka extract header metada #24367
Kafka extract header metada #24367
Conversation
@MovieStoreGuy if yo can take a look at this POC |
^^ There's lot to do in case of readability, will address it later on after the discussion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @VihasMakwana, just a few form things
@frzifus thanks for your review!! Does the core logic look alright to you? |
Just had a breef look, but at least I didn't notice anything bad 😅. Better to wait for the other reviews too. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
@MovieStoreGuy ping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A good start so far, I've left comments with regards my concerns.
What I need to see is:
- Changelog entry
- User facing docs updated (With expected use case)
- Comments addressed.
Once these are done, I am happy to approve.
955afb7
to
a374e27
Compare
a374e27
to
d7e367f
Compare
|
c760392
to
f47ba3a
Compare
Sure. Will rebase |
@MovieStoreGuy I have resolved all the conflicts and merged the main. |
@djaglowski can you have a look as well please, if it's okay for you? |
8402754
to
3514800
Compare
85d46a2
to
bc01580
Compare
@codeboten can we merge this one before the 0.86 release? it looks like an excellent feature to have. |
**Description:** Enable support to extract headers from Kafka Messages and attach them to resource attributes. In later stages in the pipeline, different exporters can utilize this information. **Link to tracking Issue:** [21729](open-telemetry#21729) **Testing:** Added test cases for logs, traces, and metrics. **Documentation:** <Describe the documentation added.> --------- Co-authored-by: Alex Boten <[email protected]>
Description: Enable support to extract headers from Kafka Messages and attach them to resource attributes. In later stages in the pipeline, different exporters can utilize this information.
Link to tracking Issue: 21729
Testing: Added test cases for logs, traces, and metrics.
Documentation: