Provide parent span for duration of transaction
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 175
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
Skunk emits a span for allocation of a session and freeing of a session but it would be nice to have a span that marks the duration of a session to track long running transactions. Some tracing tools might be able to extrapolate by subtracting pool.allocate from pool.free but Jaeger cannot.
I think something like this would work:
pool.allocate -> pool.use -> pool.free
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 the session pool code that emits the pool.allocate and pool.free spans, then trace how a session's lifetime is represented. The work is done when a parent pool.use span covers the session duration and tracing tools such as Jaeger can display it between allocation and freeing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, scala
- Domain
- database, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100