tower-rs / tower-rs/tower-http
`tower_http::trace` doc clarification regarding ingestion of parent spans from incoming requests
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 913
- Forks
- 231
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 8
Description
Does https://docs.rs/tower-http/latest/tower_http/trace/index.html also take care of ingesting the parent span/trace id from incoming requests to basically enable cross-service tracing?
That is not clear to me when reading the docs.
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 with the tower_http::trace documentation at the linked docs.rs page and verify whether incoming parent spans or trace IDs are ingested for cross-service tracing. Clarify the documented behavior and limitations so readers can tell whether this feature is supported; the issue is complete when the page answers that question unambiguously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, observability
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100