Tracing for Skunk back-end
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Scala
- Stars
- 189
- Forks
- 32
- Avg merge
- 18h 31m
- Merged PRs (30d)
- 37
Description
Tracing is always available if you're using Skunk, so we can replace SkunkMonitor with something that records events in context.
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 locating SkunkMonitor and the Skunk back-end tracing entry point. Determine how tracing events should be recorded in context and what existing behavior must be replaced; the issue does not name tests or define a completion check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100