open-telemetry / open-telemetry/opentelemetry-ruby-contrib
Additional low-level instrumentation spans created for some instrumentation libraries
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 137
- Forks
- 258
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 30
Description
Some instrumentation libraries, when enabled along with Net:Http instrumentation, generate multiple spans for a single request.
For example, both Faraday and AWS SDK instrumentation libraries generate multiple client spans (and thus multiple metrics) due to the underlying Net:Http instrumentation that is also invoked.
Would it be possible to suppress the Net:Http instrumentation in these higher level libraries such as Faraday and AWS SDK to prevent these extra spans when both libraries are enabled?
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 the Net::Http, Faraday, and AWS SDK instrumentation interactions when they are enabled together. Reproduce a single request and inspect the emitted spans and metrics. Done means higher-level instrumentation no longer produces duplicate Net::Http spans for that request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, ruby
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100