Trace Context: Apache Kafka protocol specification
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 510
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
We know that the Apache Kafka protocol is not a standard one (so recognized by organization like OASIS) but I was wondering if it could make sense to have a trace context for Kafka specification as I see for MQTT and AMQP 1.0 and how to be engaged for it.
In the end it would be simple as the other ones like using headers in a Kafka message to bring trace context related fields.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked MQTT and AMQP 1.0 trace-context specifications and comparing how they define propagation through message headers. The issue does not name repository files, tests, or a concrete deliverable; a useful next step would be to establish whether a Kafka-specific specification is wanted and define its scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100