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
Add ability in kafka-pubsub to send trace state to metadata as an option #3323
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
Still planning to work on this. Just didn't get a chance yet |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
Based on looking at code it would require to create a span and inject to metadata when publishing a raw payload but that code is in Dapr. Should we move it to Dapr kit instead? |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions. |
Describe the feature
PubSub components promote the usage of CloudEvents to include additional information in the message, including tracing information.
However, when working with existing events that do not use Cloud Events, you are losing the ability to having tracing. In some cases, when using Schema Registry, using cloud events is not an option at all... It would be a great option to be able to pass tracing information within the header. Kafka provides headers and currently any metadata added to the pubsub will be passed on as headers in the message.
I suggest providing an option in the Kafka subscription metadata to include tracing info as header automatically.
Release Note
RELEASE NOTE: ADD an option in Kafka PubSub subscription metadata to publish the tracing information as message headers
The text was updated successfully, but these errors were encountered: