neondatabase / neondatabase/serverless
OTEL tracing in driver
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 548
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
Support for OpenTelemetry in the serverless driver for transactions/individual queries would be useful to allow for full tracing from request to response of all queries my application is performing
Contributor guide
No contributing guide indexed for this repository
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 serverless driver paths for transactions and individual queries. Then determine how OpenTelemetry tracing should cover the request-to-response lifecycle, with done meaning both query types emit usable traces for the full operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postgresql, typescript
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100