typelevel / typelevel/natchez-http4s
IOLocal Tracing
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 50
- Forks
- 18
- Avg merge
- 15m
- Merged PRs (30d)
- 5
Description
The limitation with the current encoding is that its reliant on the spans. And needs the new root span for incomming requests. As well some tracing may be leveraged throughout the app. So instead we can construct it initially at the beginning of the world and then allow a "principled" modification to reset for contexts like requests etc.
If we get a FiberLocal this will be nice as this could be in the F of an app, or anything with LiftIO, but this gist displays it can be done with only an IOLocal.
IOLocal
https://gist.github.com/ChristopherDavenport/d871b8c12720fd30501c7c62efaf4167
FiberLocal
https://gist.github.com/ChristopherDavenport/66afc215d0111b2916f6eb820a3e344c
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 IOLocal and FiberLocal gists, then inspect the current span-based encoding in natchez-http4s. Clarify how tracing should be initialized and reset for incoming requests and LiftIO or Fiber contexts; done requires an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100