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
Is your feature request related to a problem? Please describe
Currently when a LoggerProvider is registered via logs.setGlobalLoggerProvider() after acquiring a logs.getLoggerProvider() elsewhere, the previously acquired LoggerProvider will stay no-op forever unless replaced manually.
Describe the solution you'd like to see
Implementing the same delegating-noop similar to the one in the trace API, where a ProxyTracerProvider and ProxyTracer delegate calls to either the registered SDK instance or a NoopTracerProvider or NoopTracer.
Is your feature request related to a problem? Please describe
Currently when a LoggerProvider is registered via logs.setGlobalLoggerProvider() after acquiring a logs.getLoggerProvider() elsewhere, the previously acquired LoggerProvider will stay no-op forever unless replaced manually.
Describe the solution you'd like to see
Implementing the same delegating-noop similar to the one in the trace API, where a ProxyTracerProvider and ProxyTracer delegate calls to either the registered SDK instance or a NoopTracerProvider or NoopTracer.
Additional context
Related to #3622
The text was updated successfully, but these errors were encountered: