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
The Named Tracers (TracerRegistry) PR has been merged now(#403), we need to update the documentation (examples and instructions) in getting-started guide.
The text was updated successfully, but these errors were encountered:
Can you provide a very brief tl;dr as to why this change from tracers to tracer registries has been made? It has to do with being able to name the tracers?
the most basic use case is disabling built-in instrumentation. Say mongodb builds opentelemetry directly into their library, but they mess it up; you can configure the tracer registry to return no-op tracers to the mongodb library.
The Named Tracers (
TracerRegistry
) PR has been merged now(#403), we need to update the documentation (examples and instructions) in getting-started guide.The text was updated successfully, but these errors were encountered: