You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.
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
The text was updated successfully, but these errors were encountered: