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 it was done for metric and tracing, the logging signal should support configuring a console exporter via config.
Proposed Solution
Add the following code and add unit tests as well.
if exporter.Console != nil && exporter.OTLP != nil {
return nil, errors.New("must not specify multiple exporters")
}
if exporter.Console != nil {
return stdoutlog.New(
stdoutlogWithPrettyPrint(),
)
}
Additional Context
This was not possible because of a change needed in the configuration schema (open-telemetry/opentelemetry-configuration@834ae3c) which has been merged, but updating the configuration package depends on #4832 to support another change in the configuration schema.
The text was updated successfully, but these errors were encountered:
Problem Statement
As it was done for metric and tracing, the logging signal should support configuring a console exporter via config.
Proposed Solution
Add the following code and add unit tests as well.
Additional Context
This was not possible because of a change needed in the configuration schema (open-telemetry/opentelemetry-configuration@834ae3c) which has been merged, but updating the configuration package depends on #4832 to support another change in the configuration schema.
The text was updated successfully, but these errors were encountered: