Standard wire format to facilitate distributed tracing
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Imagine being able to wrap a protocol handler with some kind of "decorator" that would expose two versions of the protocol: the tracing and non-tracing version.
If two peers negotiate the tracing version, libp2p would automatically handle context propagation across boundaries (i.e. on reads/writes to stream) to facilitate distributed tracing across systems.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points; begin by locating protocol negotiation and stream read/write handling in the libp2p specifications. Done would require a defined standard wire format and protocol behavior for negotiating tracing, propagating context across boundaries, and retaining a non-tracing version.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100