feat(links): write span links to Kafka #4601
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: This PR is a draft until we discuss span schema a bit further - if the schema is going to change we shouldn't create even more things to migrate by encoding links a possibly outdated way in Kafka. EAP isn't ready to start writing links into ClickHouse yet anyway.
Span links were added in #4486, but are currently only accessible as part of transaction events. We would like to get them in EAP. The first step in that process is to add them to serialized Kafka spans.
The integration tests confirm production into Kafka for every current path for links to enter the system:
span
envelope itemotel_span
envelope itemNote that our version of the
opentelemetry-proto
Python library is too old to makeflags
available so not all tests could check thesampled
handling. I'll handle that in a future PR.