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
As identified during the work for #2354, the log emitter provider doesn't have a default or noop implementation.
The text was updated successfully, but these errors were encountered:
codeboten
changed the title
The logging signal doesn't have a default log emitter provider. Should this be raised as an issue?
The logging signal doesn't have a default log emitter provider
Jan 8, 2022
Does this apply to the logging? Unlike metrics and traces, logging doesn't have an API. In case tracing/metrics user adds new instrumentation code and may need the no-op. With logging SDK, we are only taking the whatever the logs emitted and exporting them to backend. If they don't want that then they can simply remove the OTLPHandler.
As identified during the work for #2354, the log emitter provider doesn't have a default or noop implementation.
The text was updated successfully, but these errors were encountered: