Meta: Tracing
Open
Nobody has claimed this yet.
A-client
A-server
B-rfc
C-feature
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
hyper uses tracing for logging and events. This issue is meant to be a meta or tracking issue around the overall usage of tracing inside hyper. Eventually, users should be able to depend on certain spans and events. Which exactly, we need to figure out.
Relevant issues
- #2498
- Design spans specific to the server
- Design spans specific to the client
- By hyper 1.0, make
tracingsupport "unstable" if not also 1.0
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
No files or tests are named. Review the completed #2498 work and the remaining checklist, then determine the server- and client-specific spans and events that should be exposed. Done means the tracing design is agreed for both sides and the issue's remaining checklist items are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100