open-telemetry / open-telemetry/opentelemetry-ruby
Refactor Timeout.timeout for delaying the periodic metrics reader
Open
Nobody has claimed this yet.
bug
keep
metrics
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
Timeout.timeout may not be stable. It's better to use exporter its own timeout mechanism for safe exporting (e.g. otlp export on timeout)
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 with the periodic metrics reader and compare its Timeout.timeout usage with the exporter timeout handling in exporter/otlp/lib/opentelemetry/exporter/otlp/exporter.rb, especially the linked lines. Trace how exporting is delayed and determine the exporter-owned timeout behavior needed for safe periodic exporting. Done means the reader no longer relies on the unstable timeout mechanism and the relevant behavior is covered by passing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100