open-telemetry / open-telemetry/opentelemetry-ruby
Determine when Metrics Views can be instantiated
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
This issue exists to further investigate the questions raised in this thread: https://github.com/open-telemetry/opentelemetry-ruby/pull/1604/files/749a8207ac07823be5a032b2b4703c2f7380dcd1#r1683589311
When initially testing views, I was creating the instrument first and then creating the view. However, when we refactored the code to reduce the number of times we needed to collect views for a particular instrument, this process changed. Now, views must be created first and instruments created after.
Questions
- What do other languages do? Do they make the view and then the instrument?
- How do they find the views performantly?
- What does the spec say about adding views to instruments? Can a view be attached to an instrument at any time?
- What makes sense at the instrumentation level? Does that impact ideas about instantiation?
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 linked pull request diff and comment thread, then compare the OpenTelemetry specification and other language implementations as requested in the issue. Document when Metrics Views and instruments can be instantiated, how views are found efficiently, and whether views may be attached later; done means the project has a clear lifecycle decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100