Context switching between Natchez and backend instrumentation
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 340
- Forks
- 76
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 13
Description
Many of backends support auto-instrumentation for certain popular (non-Scala FP) libraries, typically using Java ThreadLocals to maintain the current span. If you're working in an app that has a tagless final / cats effect portion (where Natchez is a good fit) and also a non-FP Scala portion, it's not clear how best to propagate the span context between the two worlds in the same app.
I don't have a good solution for this, but if one exists, it would be nice to add it to the library, or at least document it. If one doesn't exist, that would also be good to document, so users can avoid frustration.
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 examining how Natchez context is propagated alongside backend auto-instrumentation that uses Java ThreadLocals. Compare the tagless-final/cats-effect portions with non-FP Scala code and determine whether a supported bridge exists. Done means documenting the supported approach or clearly recording that no solution exists.
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